From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: Better error reporting and stuff on startup
Date: Sun, 26 Sep 2010 16:14:58 -0500 [thread overview]
Message-ID: <87iq1syzot.fsf@lifelogs.com> (raw)
In-Reply-To: <87hbhcxtm6.fsf@thinkpad.tsdh.de>
On Sun, 26 Sep 2010 20:11:29 +0200 Tassilo Horn <tassilo@member.fsf.org> wrote:
TH> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>>> That makes sense for any package, but not every package should need
>>> to implement something like it. So it would be cool to extend the
>>> `message' mechanism in emacs, so that it allows for different
>>> severities (debug, info, warning?) and assign messages to packages,
>>> so that I could restrict *Messages* to show only warning messages
>>> from Gnus...
>>
>> I don't really see how that would work.
TH> Well, maybe something like
TH> (message 'gnus 'debug "Foo bar %s" (bla))
I see xdisp.c:Vmessages_buffer_name but it's not exposed to ELisp code
as a symbol. If it were, (gnus-message) could let-bind it so Gnus
messages can go to a separate *Gnus Messages* buffer. It would probably
be helpful for other packages too. I don't know if there are issues
with that besides the obvious usability problem of multiple log buffers.
Ted
next prev parent reply other threads:[~2010-09-26 21:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 14:30 Lars Magne Ingebrigtsen
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 [this message]
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=87iq1syzot.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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).