4 ms·

You answered your own question?

• amichail 4y ago
  How is that? I expect an app to quit immediately via cmd-q.
• anigbrowl 4y ago
  No. The question was not 'how do I force the app to terminate' but 'why doesn't it terminate in the normal fashion?' A lot of tech people have a very bad habit of ignoring the question that was asked and answering one they think was meant, or a related question that they happen to have an answer to. This isn't helpful to the person asking the question.
  • theCrowing 4y ago
    It works as intended the dev can choose if he wants to invoke NSTerminateNow, NSTerminateCancel or NSTerminateLater if someone hits cmd+q. Writing condescending comments instead of contributing to the topic is also really helpful. bleh.
    • amichail 4y ago
      My reason for quitting Podcasts is to reduce CPU usage from the refresh. Having to quit it from Activity Monitor after cmd-q is very annoying.
      • theCrowing 4y ago
        You can force close it instead of Command+q by using Option+Command+Esc. @anigbrowl looks like the question really was how he can force close it..........
        • amichail 4y ago
          Interestingly, you don't need to force quit in Activity Monitor. After cmd-q in Podcasts, sending a normal quit signal via Activity Monitor works.
          • theCrowing 4y ago
            It's mainly because Activity Monitor and Force Close Apps send "terminate" instead of the "applicationShouldTerminate" from cmd+q.
            • amichail 4y ago
              Thanks for clarifying the issue! I consider this a bug in Podcasts then since a refresh can be very CPU intensive and the user would naturally quit the app to reduce CPU usage but doing that surprisingly doesn't work.