GNU bug report logs - #6088
Please record all warnings and errors in the *messages* buffer

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 6088 in the body.
You can then email your comments to 6088 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Lennart Borgman <lennart.borgman <at> gmail.com>
To: Emacs Bugs <bug-gnu-emacs <at> gnu.org>
Subject: Please record all warnings and errors in the *messages* buffer
Date: Mon, 3 May 2010 14:44:31 +0200

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.

Message #8 received at 6088 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> jurta.org>
To: Lennart Borgman <lennart.borgman <at> gmail.com>
Cc: 6088 <at> debbugs.gnu.org
Subject: Re: bug#6088: Please record all warnings and errors in the *messages*
	buffer
Date: Wed, 05 May 2010 21:31:12 +0300

> 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/

Message #11 received at 6088 <at> debbugs.gnu.org (full text, mbox):

From: Lennart Borgman <lennart.borgman <at> gmail.com>
To: Juri Linkov <juri <at> jurta.org>
Cc: 6088 <at> debbugs.gnu.org
Subject: Re: bug#6088: Please record all warnings and errors in the *messages*
	buffer
Date: Wed, 5 May 2010 20:59:53 +0200

On Wed, May 5, 2010 at 8:31 PM, Juri Linkov <juri <at> 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'.

Message #14 received at 6088 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> jurta.org>
To: Lennart Borgman <lennart.borgman <at> gmail.com>
Cc: 6088 <at> debbugs.gnu.org
Subject: Re: bug#6088: Please record all warnings and errors in the *messages*
	buffer
Date: Wed, 05 May 2010 22:14:14 +0300

>>> 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/

Message #17 received at 6088 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Lennart Borgman <lennart.borgman <at> gmail.com>
Cc: 6088 <at> debbugs.gnu.org
Subject: Re: bug#6088: Please record all warnings and errors in the
 *messages* buffer
Date: Thu, 20 Aug 2020 20:32:36 +0200

Lennart Borgman <lennart.borgman <at> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.