Terminal – How to ‘killall’ Visual Studio Code

bashcommand lineterminal

I have a small shell script called "k" that i call everytime when i want to reset my complete Development Cycle:

killall node
killall Xcode
killall Terminal

How can i find out the final name of the "Visual Studio Code"-Prozess to kill it also this way?

I've tried:

killall "Visual Studio Code"

No matching processes belonging to you were found

killall "Code"

No matching processes belonging to you were found

Any ideas?
I am looking for a generic approach without any manually lookup of PIDs necessary.

This application looks like this in Activity Monitor:

Best Answer

I have Visual Studio Code, version 1.1.1, installed and on my system the following works for me:

kill -9 $(pgrep Electron)

Update: Just tested with Visual Studio Code, version 1.14.1, under macOS 10.12.5 and the above command closes Code and Code Helper that show in Activity Monitor.

PS: killall Electron also works.

Related Solutions

MacOS – Disable visual bell animation in Terminal

Go to the "Terminal" menu
Select "Preferences"
Select "Settings" at the top
Select "Advanced" at the right
Uncheck "Visual Bell"

Terminal preferences - Settings - Advanced

macOS – Understanding ‘-HUP’ in Terminal, Bash, and Command-line Environment

The -HUP option is the signal that's sent to the processes by the killall command. It can be a little hard to tell, but the relevant entry in the killall manual is:

-SIGNAL     Send a different signal instead of the default TERM.  The signal may be specified
            either as a name (with or without a leading SIG), or numerically.

The difference between the default TERM signal that killall sends and the HUP signal depends largely on the program you're sending the signal to. At the program end, they receive a different interrupt signal value. So the program can catch the interrupts and decide, based on the value, if they should do one thing or the other.

The TERM signal (historically the "terminate signal") is usually sent to a program to request its termination (which is a politer version of forcing its termination with the KILL signal). The program is free to catch and ignore the TERM signal. It doesn't have to terminate if it doesn't want to and it can completely ignore this signal.

The HUP signal (historically the "hangup signal") is usually sent to a program to request that it restarts and re-reads all its configuration in the process. The actual behaviour of the program depends on the program-specific implementation. Not all programs catch HUP and they aren't required to by convention or dogma. For example, the Apache web server will catch a HUP signal and re-read all its configuration files but it won't restart any processes.

If you want to truly terminate the processes and not worry about whether they're going to catch and obey the signal uses the KILL signal. It cannot be caught or ignored and results in process termination.

For a good review of available POSIX signals see this Wikipedia article.

Best Answer

Related Solutions

MacOS – Disable visual bell animation in Terminal

macOS – Understanding ‘-HUP’ in Terminal, Bash, and Command-line Environment

Related Question