Closed NightMachinery closed 3 years ago
Sorry, this seems to have been caused by my Doom popup config, where popup buffers by default will be killed after some time.
It's fixable by adding :ttl nil
, if anyone does the same mistake as me.
(set-popup-rule! "^\\*Racket REPL.*\\*$" :ignore nil :height 0.5 :select nil :ttl nil)
Interesting. If you manually kill-buffer
a buffer associated with an Emacs process, normally you get a warning y/n prompt.
Is Doom popup intentionally bypassing that prompt, because it would be annoying to get prompted at some random time while you're working on something else?
That seems harmless and maybe even desirable for e.g. some forgotten *shell*
buffer sitting at a prompt doing nothing for a long time. But if the *shell*
buffer is running some long task you wanted to finish, I don't know about killing it with no prompt?
So I wonder if Doom popup already has (or should get) a configuration option to avoid auto-killing buffers associated with a process?
I frequently get
[ info] racket-mode: get-interaction: eof
.Here is `Racket Logger: