devs/cproof
1
2
Fork 1
Code Issues 43 Pull Requests 9 Actions Packages Projects 1 Releases Wiki Activity

remove SIGUSR1 escape; pkill <editor> is the standard recovery
All checks were successful
CI Code / Check coding style (pull_request) Successful in 32s
Details
CI Code / Check spelling (pull_request) Successful in 19s
Details
CI Code / Linux (debian) (pull_request) Successful in 4m30s
Details
CI Code / Code Coverage (pull_request) Successful in 3m15s
Details
CI Code / Linux (ubuntu) (pull_request) Successful in 4m36s
Details
CI Code / Linux (arch) (pull_request) Successful in 6m21s
Details

Browse Source 
The SIGUSR1 -> editor_emergency_kill wiring was a contrived escape
hatch. A console user with a stuck editor reaches for kill / pkill /
SIGKILL on the editor, not undocumented signals on the chat client.
editor_emergency_kill() stays for the internal Ctrl-Z abort path.
This commit is contained in:
jabber.developer2
2026-05-31 15:12:40 +03:00
parent 3f91cbc8b0
commit b90dec5be3
3 changed files with 3 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/tools/editor.h
View File

@@ -16,9 +16,7 @@
gboolean launch_editor(gchar* initial_content, void (*callback)(gchar* content, void* data), void* user_data);
// SIGUSR1 escape: SIGTERM the editor child. Use when WUNTRACED can't catch
// it (alive but stuck). Wired in profanity.c.
void editor_emergency_kill(void);
void editor_emergency_kill(void); // SIGCONT+SIGTERM the editor child
// TRUE if editor child is STOPPED (Ctrl-Z / :stop / gdb-attach). Does not
// reap; g_child_watch keeps handling exit.