bug#6088: Please record all warnings and errors in the *messages* buffer

bug#6088: Please record all warnings and errors in the *messages* buffer

[Lennart Borgman]

Could we please coordinate warnings, errors and messages? This could
make it more easy to find errors.

I suggest as a simple first step to record all errors and warnings in
the message buffer.

For warnings this is very simple. Just move the code for
noninteractive in display-warnings so that it is always run.

For errors this means outputting a message even when debug-on-error is
non-nil. I am not sure how to do that.

bug#6088: Please record all warnings and errors in the *messages* buffer

[Juri Linkov]

> Could we please coordinate warnings, errors and messages? This could
> make it more easy to find errors.
>
> I suggest as a simple first step to record all errors and warnings in
> the message buffer.
>
> For warnings this is very simple. Just move the code for
> noninteractive in display-warnings so that it is always run.

Do you mean to duplicate messages from the *Warnings* buffer to the
*Messages* buffer?

> For errors this means outputting a message even when debug-on-error is
> non-nil. I am not sure how to do that.

Do you want this for `error' or for your new function `user-error'?

-- 
Juri Linkov
http://www.jurta.org/emacs/

bug#6088: Please record all warnings and errors in the *messages* buffer

[Lennart Borgman]

On Wed, May 5, 2010 at 8:31 PM, Juri Linkov <juri@jurta.org> wrote:
>> Could we please coordinate warnings, errors and messages? This could
>> make it more easy to find errors.
>>
>> I suggest as a simple first step to record all errors and warnings in
>> the message buffer.
>>
>> For warnings this is very simple. Just move the code for
>> noninteractive in display-warnings so that it is always run.
>
> Do you mean to duplicate messages from the *Warnings* buffer to the
> *Messages* buffer?

Yes, that is a good beginning.

>> For errors this means outputting a message even when debug-on-error is
>> non-nil. I am not sure how to do that.
>
> Do you want this for `error' or for your new function `user-error'?

For `error'.

bug#6088: Please record all warnings and errors in the *messages* buffer

[Juri Linkov]

>>> For errors this means outputting a message even when debug-on-error is
>>> non-nil. I am not sure how to do that.
>>
>> Do you want this for `error' or for your new function `user-error'?
>
> For `error'.

Why not for `user-error'?  It is intended for user-level errors,
so users might want to be able to find there errors in the
*Messages* buffer.

-- 
Juri Linkov
http://www.jurta.org/emacs/

bug#6088: Please record all warnings and errors in the *messages* buffer

[Lars Ingebrigtsen]

Lennart Borgman <lennart.borgman@gmail.com> writes:

> Could we please coordinate warnings, errors and messages? This could
> make it more easy to find errors.
>
> I suggest as a simple first step to record all errors and warnings in
> the message buffer.

I think it would be confusing for the *Warnings* stuff to show up in
*Messages*, too.

> For errors this means outputting a message even when debug-on-error is
> non-nil. I am not sure how to do that.

If debug-on-error is nil, it looks like the error messages already end
up in the *Messages* buffer.  When we have debug-on-error non-nil, I
don't quite a use case for doing that, and it would be a bit
inconsistent: We haven't actually shown the error message, so putting it
in the *Messages* buffer doesn't seem quite right.

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no