diff options
author | Cole Helbling | 2023-03-13 12:08:57 +0000 |
---|---|---|
committer | GitHub | 2023-03-13 12:08:57 +0000 |
commit | 34934733b364ed460c647f1775f5865048833f54 (patch) | |
tree | 7e1172cd74b23364d2465141149a28d1459c4bdc /runtime/themes/tokyonight_storm.toml | |
parent | 4f066b1cc628e2d3c69da9bdd0b16f1a8e74ce6f (diff) |
helix-term: send the STOP signal to all processes in the process group (#3546)
* helix-term: send the STOP signal to all processes in the process group
From kill(3p):
If pid is 0, sig shall be sent to all processes (excluding an unspecified set
of system processes) whose process group ID is equal to the process group ID
of the sender, and for which the process has permission to send a signal.
This fixes the issue of running `git commit`, attempting to suspend
helix with ^Z, and then not regaining control over the terminal and
having to press ^Z again.
* helix-term: use libc directly to send STOP signal
* helix-term: document safety of libc::kill
* helix-term: properly handle libc::kill's failure
I misread the manpage for POSIX `kill` -- it returns `-1` in
the failure case, and sets `errno`, which is retrieved via
`std::io::Error::last_os_error()`, has its string representation printed
out, and then exits with the matching status code (or 1 if, for whatever
reason, there is no matching status code).
* helix-term: expand upon why we need to SIGSTOP the entire process group
Also add a link back to one of the upstream issues.
Diffstat (limited to 'runtime/themes/tokyonight_storm.toml')
0 files changed, 0 insertions, 0 deletions