A 0 next to a category means it isnt active, but a 1 means that this assertion is.
(By 'temporarily,' the documentation means the change does not survive a restart. Some apps and processes can keep your Mac awake indefinitely. That's arguably a superior method to disabling App Nap system-wide, as it seems just as resistant to the 'disappearing checkbox' syndrome. What makes the Mac ideal for getting work done is that you can have multiple Mac apps open at the same time, all of them chugging away at the. When all of these conditions are met the app is placed on a scheduling queue that rarely gets actual time on the CPU.The app wakes up automatically when the user brings the app to the foreground or when the app receives a Mach message or Apple event.The documentation goes on to describe the coding the developer needs to employ to opt out of having his application be subject to App Nap's invocation, adding Note: If you experience problems with App Nap, you can temporarily disable it for a particular process by typing: defaults write NSAppSleepDisabled -bool YES It has not taken any power management assertions.
The Apple Developer Documentation on App Nap explains it this way: An app is considered to be a candidate for sleep if:
