Know which .plist's are disabled #22
Description
When you "lunchy start -w myservice" or "lunchy stop -w myservice" the state is saved for next boots. In the past days launchctel was adding a key to the .plist file with the value "Disabled", but since SnowLeopard the .plist file is not changed and it is store elsewhere.
As far as I know, launchctl does not offer a way to know if a .plist file is disabled or not for next boots and having to reboot is tedious... It would be great to have some way to see which .plists are disabled or not.
The "lunchy status" command seems the more appropiated place to me for showing it but since it uses the "launchctl list" output, it would be fair enough something like "lunchy disabled".
A link to an article that explains the new locations where the disabled keys are stored:
http://www.mactech.com/articles/mactech/Vol.25/25.10/2510MacEnterprise-SnowLeopard-launchdandLunch/index.html