While debugging these lisp changes with Edebug, I noticed that `g' 
(top-level)
    didn't clear Edebug's arrow.

The natural way to do that is with an unwind-protect around the code
that reads the input.  Would you like to add one?


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

Reply via email to