> 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?
You will have to explain further, I don't understand what is causing the
problem. The code around input to what?
I meant the code in edebug to read input.
But now I think I misunderstood before.
The g key can run a command that clears the arrow
and then calls top-level.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
