From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Better error reporting and stuff on startup
Date: Sun, 26 Sep 2010 16:30:19 +0200 [thread overview]
Message-ID: <m3d3s0efwk.fsf@quimbies.gnus.org> (raw)
Today you get a lot of messages displayed for microseconds on Gnus
startup, and any error messages are just sort of hidden there.
Would it make sense for Gnus to (kind of) collect all the "important"
messages (to be determined somehow), and then display them at the end?
Somehow?
Hm.
We could have a global variable `gnus-important-messages' that
`gnus-message' pushes things onto if the message level is low? And then
`M-x gnus' could bind that variable, and then display the contents after
startup? Just with `message'?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next reply other threads:[~2010-09-26 14:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 14:30 Lars Magne Ingebrigtsen [this message]
2010-09-26 15:24 ` Didier Verna
2010-09-26 15:33 ` Lars Magne Ingebrigtsen
2010-09-26 16:29 ` Didier Verna
2010-09-26 16:31 ` Lars Magne Ingebrigtsen
2010-09-26 16:58 ` Frank Schmitt
2010-09-26 17:06 ` Lars Magne Ingebrigtsen
2010-09-27 7:21 ` Didier Verna
2010-09-27 16:44 ` Lars Magne Ingebrigtsen
2010-09-26 15:52 ` Julien Danjou
2010-09-26 17:22 ` Tassilo Horn
2010-09-26 17:24 ` Lars Magne Ingebrigtsen
2010-09-26 18:11 ` Tassilo Horn
2010-09-26 21:14 ` Ted Zlatanov
2010-09-26 21:17 ` Lars Magne Ingebrigtsen
2010-09-26 17:51 ` Rupert Swarbrick
2010-09-26 21:20 ` Richard Riley
2010-09-27 7:26 ` Didier Verna
2010-09-27 16:45 ` Lars Magne Ingebrigtsen
2010-09-26 18:19 ` Dan Christensen
2010-09-26 20:12 ` Dan Christensen
2010-09-26 20:42 ` Lars Magne Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3d3s0efwk.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
/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.
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 NNTP newsgroup(s).