From: Lars Ingebrigtsen <larsi@gnus.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 6088@debbugs.gnu.org
Subject: bug#6088: Please record all warnings and errors in the *messages* buffer
Date: Thu, 20 Aug 2020 20:32:36 +0200 [thread overview]
Message-ID: <87tuwxmam3.fsf@gnus.org> (raw)
In-Reply-To: <x2ye01d8a51005030544gfd34afcdge33cdcaaa696b17c@mail.gmail.com> (Lennart Borgman's message of "Mon, 3 May 2010 14:44:31 +0200")
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
prev parent reply other threads:[~2020-08-20 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 12:44 bug#6088: Please record all warnings and errors in the *messages* buffer Lennart Borgman
2010-05-05 18:31 ` Juri Linkov
2010-05-05 18:59 ` Lennart Borgman
2010-05-05 19:14 ` Juri Linkov
2020-08-20 18:32 ` Lars Ingebrigtsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tuwxmam3.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=6088@debbugs.gnu.org \
--cc=lennart.borgman@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).