Re: two related edebug problems

[Stefan Monnier]

> I found out the cause of the bug.  edebug-display calls sit-for to
> pause before displaying eval results, then calls
> edebug-recursive-edit.  However, edebug-recursive-edit rebinds
> unread-command-events, causing sit-for interruptions (which are put
> into unread-command-events) to go unnoticed.  This creates problems
> when you type in edebug commands in quick succession.  I fixed this by
> moving the rebinding of unread-command-events to edebug-display.

This is a workaround rather than a fix.  A real fix would be to change
sit-for so it doesn't use unread-command-events but an internal variable
instead with which other code can't mess.


        Stefan