Re: if and only if an Error message

[Michael Heerdegen]

Emanuel Berg <embe8573@student.uu.se> writes:

> > did you quit the debugger the first time and return
> > to the toplevel?  If not, then what you see is
> > expected - a new debugging session is not started
> > when a session is already active, because that would
> > be annoying while debugging.
>
> I did close the backtrace buffer. I can bring it back
> with `debug' but it doesn't report the new errors, and
> old stuff still there.

It doesn't suffice to close the window, you must quit the debugger with
q.  Even killing the debugger buffer doesn't bring you back to the
top-level.

> Do you know how to just have all error messages in a
> separate buffer, and never bring up the debugger unless
> I say so?

Like (setq debug-on-error nil)?  But this doesn't use a separate buffer,
it uses *Messages*.