Timeline for How to automatically open the debugger whenever `kill-buffer` is invoked?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2021 at 13:10 | comment | added | Drew |
What @phils said. The answer tells you how to do it, but it's better to tell you that you probably don't want to do it, except maybe briefly, just to see which function initially invoked kill-buffer.
|
|
| Jun 16, 2021 at 22:18 | comment | added | phils |
Buffers are a data type in Emacs -- they are created and killed behind the scenes all the time. Consider the with-temp-buffer macro, for instance. You can expect kill-buffer to be called frequently.
|
|
| Jun 16, 2021 at 21:59 | comment | added | patfla | Thanks - that's useful - although it's already raising new questions. It opens a Backtrace buffer with the call stack. It seems that elpy is very sensitive to this - just scrolling through my source file provokes breaks into Backtrace. Then if I attempt to move the mouse from the source buffer to Backtrace, Backtrace disappears. ... I wrote more .. but stackex tells me "too long by 400 chars." Ah - pastebin.com/YjP0FNcw | |
| Jun 16, 2021 at 20:40 | history | answered | Drew | CC BY-SA 4.0 |