You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related: when edebug is active, any buffer with lispy active will forward to edebug, i.e. if the point is at |(some-func) in a common lisp buffer and I type f, then special-lispy-flow is called and rather than calling lispy-flow in my common lisp buffer, it calls edebug-forward-sexp in whatever buffer edebug is running in.
I think lispy--edebug-commandp should check that edebug-mode (which is buffer-local) evals to t, since edebug-active is not buffer local. That change fixed the problem for me.
Steps to reproduce:
(add-hook 'eval-expression-minibuffer-setup-hook 'lispy-mode)
to enablelispy-mode
inM-:
edebug
somewheree
(edebug-eval-expression
)Expected
" " is typed
Result
Message:
Edebug will stop at next stop point.
. Nothing is typed in the prompt.The text was updated successfully, but these errors were encountered: