Julia EvansAug 26, 2024

what are some problems with quitting programs in the terminal you’ve run into? so far I have:

- not knowing how to quit vim (or some other program like nano etc)
- programs not responding to ctrl c
- a background program being killed when you close your shell

what am i missing?

Show threaddr 🛠️🛰️📡🎧

@b0rk Sometimes if C-c doesn't work I'll C-z. In theory, 'jobs' shows that job, but I don't know how to kill from there.

So I use ps | grep, but it can be a hassle.

And if there's a subprocess, I get <defunct>s and a mess.

Aug 26, 2024 at 7:15pmWeb
Show threadWyatt (🏳️‍⚧️♀?)Aug 26, 2024
@davidr @b0rk C-\ is usually the right move if C-c doesn't work. C-z tends to just send stuff to the background.
Show threaddr 🛠️🛰️📡🎧Aug 26, 2024
@wyatt8740 @b0rk Huh, I've never heard of C-\. I'll try to remember that one
Show threadHarry PercivalAug 26, 2024
@davidr @wyatt8740 @b0rk same TILLLLL thank you <3
Show threadWyatt (🏳️‍⚧️♀?)Aug 26, 2024
@davidr @b0rk it sends SIGQUIT which is stronger than SIGINT. :)
C-d for SIGHUP can also be useful to try but sigquit is more likely to worki.
Show threadStephenAug 26, 2024
@davidr @b0rk for the record:

$ kill -9 %1

will kill the first backgrounded job.
Show threadStephenAug 26, 2024
@davidr @b0rk also when I was first learning I suffered the inverse - I was trying "undo" and typed ctrl-z, thereby sending vim into the background, and I had no idea how to bring it back!
Show threaddr 🛠️🛰️📡🎧Aug 26, 2024
@stephen @b0rk MS hijacking C-a to "select all" when I want to edit the beginning of a line has lost me a LOT of email bodies.