Timeline for How to stop a process gracefully before killing its buffer?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 1, 2023 at 21:24 | vote | accept | Arch Stanton | ||
| Mar 31, 2023 at 8:49 | comment | added | Arch Stanton | @phils What do you think of my answer? Did I miss something? | |
| Mar 31, 2023 at 8:40 | answer | added | Arch Stanton | timeline score: 1 | |
| Mar 30, 2023 at 11:08 | comment | added | phils | I'll leave you to research that; no time to follow up right now. It's more complex than the other option. | |
| Mar 30, 2023 at 11:07 | comment | added | phils |
C-h i g (elisp)Signals to Processes regarding kill-process and friends.
|
|
| Mar 30, 2023 at 11:07 | comment | added | Arch Stanton | Hi @phils :-) > You could use a process sentinel to kill the associated buffer as soon as the process reports that it has exited. I was thinking about that so I read about process sentinels in the manual, but I can't figure out how to do it. Can you tell me, please? | |
| Mar 30, 2023 at 11:01 | comment | added | phils |
You could use a process sentinel to kill the associated buffer as soon as the process reports that it has exited. Or you could simply assume that the process will exit and wait for that to happen, something like (when-let ((proc (get-buffer-process (current-buffer)))) (while (buffer-live-p proc) (sit-for 0.1)))
|
|
| Mar 30, 2023 at 10:47 | comment | added | Arch Stanton | Somewhat related: stackoverflow.com/questions/20339604/… | |
| Mar 30, 2023 at 10:00 | history | asked | Arch Stanton | CC BY-SA 4.0 |