Skip to main content

Module process

Module process 

Source
Expand description

Process search, behind the kill keyword.

Typing kill fire lists the user’s own processes whose name or command line matches, heaviest first; activating one sends SIGTERM, and the frontend offers SIGKILL as a secondary action. Behind a keyword rather than always-on for the same reason clipboard history is: a result whose activation kills something must never appear next to results whose activation opens something.

The listing is a plain /proc walk, done fresh per keystroke. A few hundred processes at two small files each is well under a millisecond of I/O, and a cache would only be a way to offer a process that has already exited.

Functions§

matching
The user’s own processes matching needle, heaviest first.
terminate
Ask a process to exit, or make it.