News for hackers. Stuff that matters.
Re:Ctrl-C by klez on Saturday August 06, 2022 @07:43AM (#32367199)
Which is exactly what the author is saying shouldn't be needed.
Re:Ctrl-C by dmarinus on Saturday August 06, 2022 @07:52AM (#32367276)
Author is talking about looking up PIDs, kill -9 %1 saves you from that.
Re:Ctrl-C by kragen on Saturday August 06, 2022 @10:38PM (#32373394)
It may not be %1; if the shell says

    [2]+  Stopped                 units
it's %2. But it's also %+, %%, and just %, which is what the "+" after the [2] means. In my case %1 is evince zhegalkin-sm7433.pdf (Running, not Stopped), which I definitely do not want to kill.

Plenty of people open a new terminal window for every new program they want to run, but I commonly have several "jobs" in the same window, stopped or even running. Less often now that monitors are bigger, but still.

Re:Ctrl-C by kcl on Saturday August 06, 2022 @07:59AM (#32367310)
It is true this improves the bad path. It ignores desired happy path cases: downstream processes, custom debugging, graceful shutdown, preserved workspaces, and so on.