Re: Edebug: avoid messages on 'f' command

[Alan Mackenzie]

Hello, Richard.

On Sat, May 07, 2016 at 02:40:32PM -0400, Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]

>   > > Wouldn't setting edebug-execution-mode to 'Continue-fast also remove 
> this
>   > > pause, even before this commit was made?

>   > Copying RMS on this. Looks like this pause at braekpoint was (sit-for 1)
>   > from the very beginning (circa 1993-1996).

> I don't remember anything about that call to sit-for from 20 years ago.
> But I have a guess why it is there: because without it, execution would
> be so fast you couldn't even see things scroll past.  So you might as well
> proceed at full speed.

The commands `t' (`edebug-trace-mode') and `c' (`edebug-continue-mode'),
which pause 1 second at, respectively, each stop point and each
breakpoint, are unaffected by this setting - they use one or more
different instances of `sit-for' which are on other code paths.

> If that mode is useful for you, I have nothing against supporting it.
> I think it would not be very useful in general, so I would not make
> it the default.

The setting at issue affects only the `f', `o', 'h' and `g' commands,
all of which stop at the next breakpoint and wait for another command.
When they do so, they display "Break" for one second and only then do
they display the result of the form just evaluated.  This is irritating.

I'm not unconvinced that removing this 1 second pause by default would
be the Right Thing.

> -- 
> Dr Richard Stallman
> President, Free Software Foundation (gnu.org, fsf.org)
> Internet Hall-of-Famer (internethalloffame.org)
> Skype: No way! See stallman.org/skype.html.

-- 
Alan Mackenzie (Nuremberg, Germany).