Gracefully Close an Application from the Command Line in Mac OS X
Quitting apps gracefully is typically done through the appropriate application menu by choosing “Quit”, but the Mac GUI is obviously inaccessible from the command line of Mac OS X. So when most command line users are confronted with the need to exit an application, they wind up using the ‘kill’ command to terminate the process and forcibly quit the app, rather than issuing a ‘soft’ kill. The obvious problem with terminating an app is that while it does exit the application, you may lose data in that process, and even session restoration caches may not be adequate to restore the data. Thus, whenever possible, it’s usually best for users to gracefully quit an application instead.
Though it’s not particularly well known, you can send a standard quit signal to any Mac OS X GUI app from the command line with the assistance of the osascript command. It’s fairly easy to use, and that’s what we’ll cover here.
How to Gracefully Quit Apps from the Terminal in Mac OS X with osascript
Again, this will issue a standard quit signal to an application, rather than a kill (terminate) signal. That also means the target application won’t forcibly exit if there is unsaved data without prompting the user for input (unless you have auto-save setting enabled for Mac OS X and the application doesn’t prompt the user as a result).
The basic syntax to send a standard quit signal to a GUI application in Mac OS X from Terminal is as follows:
osascript -e 'quit app "APPLICATIONNAME"'
For example, to quit Calendar from the command line, replace APPLICATIONNAME with “Calendar”
osascript -e 'quit app "Calendar"'
Because Calendar syncs and doesn’t have a save option, you won’t be presented with the standard save dialog when trying to close the app. With apps that do have save options and when Mac OS X has auto-save disabled, the save dialog box will be summoned as usual.
Another advantage to using osascript to close apps gracefully is that you can provide an actual application name, which is much easier to remember and quite a bit more user friendly than relying entirely on process ID numbers that go with the kill command. Note that modern versions of Mac OS X offer an improved kill command that is more user friendly, known as pkill.
You could use this in a bash script to close out applications from the command line, or even modify it to behave similarly to the “Quit All Open Apps” with Automator trick we covered a while back.
Never knew about osascript. This was helpful! Thanks!
Is there a way to close an app that is running under another user?
Yeah i am looking for it too :/
Yanko
Yes absolutely, you can terminate other user processes with the pkill command! Let’s say the username is “Bob” then it would be
sudo pkill -u Bob *
Here’s an article on this topic:
https://osxdaily.com/2013/02/18/kill-all-processes-belonging-to-user/
The above was supposed to be a reply to Joseph…
It should, but it would rely on having trapped signal 3 and turning it into a quit event. If that’s the default for the commonly used frameworks? If not, kill -3 just terminates the process. In contrast, doing it via osascript triggers the actual quit function.
PS the documentation says you can’t call Cocoa functions from signal handlers.
“Gracefully” quit an app? You need to kill! Kill! Kill! Kill!
Easy there, Marine.
kill -3 [pid] should do the same thing
Or rather, even a kill [pid] may do the job.
Here’s a quick bash script using osascript though:
quit () {
for appname in $*; do
osascript -e ‘tell app “‘$appname'” to quit’
done
}
so then you can just type ‘quit appname’ to do the same thing
here is an updated version that might work better for some people:
function quit () {
if [ -z “$1” ]; then
# display usage if no parameters given
echo “Usage: quit appname”
else
for appname in $1; do
osascript -e ‘quit app “‘$appname'”‘
done
fi
}