Re: if and only if an Error message

[Emanuel Berg]

Michael Heerdegen <michael_heerdegen@web.de> writes:

>> OK, I just found another variable, inhibit-debugger,
>> sounds interesting as well...
>
> But that one is not intended to be set by the user.

OK, if that is harmful (?) perhaps it should be
mentioned in the documentation:

    Non-nil means never enter the debugger.  Normally
    set while the debugger is already active, to avoid
    recursive invocations.

>> *Messages* is in fundamental-mode, and there seems
>> to be no special notation for errors, so they can't
>> be filtered and/or highlighted that way either...
>
> Is that really so much useful?  Anyway, you could set
> command-error-function' to do what you want.

OK, will do! Yes, it is useful so I can study the error
messages and see if any of them is something that I'd
care to analyze and/or fix. Now I'm basically unaware
of them (if they even exits).

-- 
underground experts united