From: Didier Verna <didier@xemacs.org>
To: ding@gnus.org
Subject: Re: Better error reporting and stuff on startup
Date: Mon, 27 Sep 2010 09:21:15 +0200 [thread overview]
Message-ID: <muxd3rztzx0.fsf@uzeb.lrde.epita.fr> (raw)
In-Reply-To: <m3bp7kzct7.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 26 Sep 2010 18:31:32 +0200")
Lars Magne Ingebrigtsen wrote:
> No, most of them are just that one of the 13 servers you're connecting
> to didn't respond. It's nice to know that it happened, but it's not an
> exceptional situation.
I'm not convinced, but anyway here's another idea: there are other
ways (than messages) to convey information to the user. For instance, I
use a hack that will display every group in the *Group* buffer in red if
the server denied or closed the connection.
Here goes:
;; Highlight group buffer lines according to the server status. With this, you
;; can choose to fontify group lines according the current status of the
;; group's server. Caveat: a server status change will not be immediately
;; visible in the group buffer. It has to be updated, for instance by getting
;; new mail.
;; How it works: the advice below adds a `server-status' local variable that
;; can be used in `gnus-group-highlight'. For instance, you can use forms like
;; (eq server-status 'closed) or (eq server-status 'denied) in conjunction
;; with the two following faces:
(defface gnus-group-server-denied-face '((t ()))
"Face used for groups belonging to a denied server."
:group 'gnus-group)
(defface gnus-group-server-closed-face '((t ()))
"Face used for groups belonging to a denied server."
:group 'gnus-group)
(defadvice gnus-group-highlight-line (around server-status activate)
"Add a SERVER-STATUS local variable for use in `gnus-group-highlight'."
(let (server-status)
;; Let's do this outside the let to avoid a load-time warning
(setq server-status (gnus-server-status
(gnus-find-method-for-group
(gnus-group-group-name))))
ad-do-it))
--
Resistance is futile. You will be jazzimilated.
Scientific site: http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com
next prev parent reply other threads:[~2010-09-27 7:21 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 [this message]
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=muxd3rztzx0.fsf@uzeb.lrde.epita.fr \
--to=didier@xemacs.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).