- Thanks - that's useful - although it's already raising new questions.
- It opens a *Backtrace* buffer with the call stack. It seeems 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.
- Other modes don't seem to provoke this sensitivity. Reading the top of a *Backtrace* call stack, I think what elpy is doing is _very_ frequently opening, using, then deleting temp buffers. I wasn't able to snip an image of *Backtrace* using Windows (*Backtrace* closes too quickly) so took a camera photo:
- seems I'm down in elpy-rpc at get_calltip_or_oneline_docstring, this triggers something in some json functions - and these, eventually, trigger a kill-buffer on buffer names of form *temp*-nnnnnn.
- Hmm. Going to the web seems I should be able to directly enter single-letter commands into *Backtrace* but if I try this *Backtrace* immediately disappears (closes one assumes).
RAW Paste Data