Re: debug-ignored-errors usage

[Stefan Monnier]

> So the debugger is only triggered once per error type?

That's probably because you're still in the debugger of the first error,
in which case the debugger is temporarily inhibited.

> Also, putting beginning-of-buffer in `debug-ignored-errors' still
> echoes "Beginning of buffer" in the minibuffer when that happens.

Why is that a surprise?
Do you really consider echoing "Beginning of buffer" as "debugging"?

> but you still get the message every time like always?

The error message is there to let the user know about what happened.
The debugger is there so you can go and change the code to avoid the error.

In the case of beginning-of-buffer, the error is usually not due to
a problem in the code, but a problem in the user's action, which is why
it's placed in debug-ignored-errors (there's usually no point entering
the debugger for that condition since it does not reflect a bug that
we'd want to track down).

> I don't see the point in seeing the message in
> the echo area either.

Many/most commands try to make sure that *something* happens in response
to the command, so the user knows that the command was indeed executed.
Echoing is one way to do that when the command wouldn't do
anything else otherwise.


        Stefan