From: Ben Kibbey <bjk@luxsci.net>
To: info-gnus-english@gnu.org
Subject: Re: A Gnus Biff
Date: Sat, 29 Sep 2012 00:13:30 -0400 [thread overview]
Message-ID: <87lifteaad.fsf@luxsci.net> (raw)
In-Reply-To: <mailman.9955.1348869546.855.info-gnus-english@gnu.org>
William Gardella <gardellawg@gmail.com> writes:
> Hey,
>
> I'm in the process of writing a simple "biff" for Gnus, to notify me if
> one or more of a list of designated Gnus groups has unread messages in
> it (see below). So far it crudely works, and is suitable for use
> interactively or by `display-time-mail-function' if you want "Mail" to
> appear in the mode line for Gnus messages instead of mails in your local
> mailspool. What it doesn't have as yet, as you'll see, is very good
> error handling.
It may be off-topic to the subject, but I wish someone would redo
maildir support in Emacs to handle message flags. I have maildir
mailboxes and use conky to show mailbox status (new messages) then call
gnus-group-get-new-news to refresh the mailbox display after the
messages have been retrieved from fetchmail. The problem is that each
message status is overwritten by gnus (no longer new to conky) and I am
no longer notified of new messages on any workspace (sawfish) until I
visit the gnus frame in another workspace.
I could prevent refreshing the gnus mail status by preventing the
gnus-group-get-new-news call (emacsclient) and keep the conky message
status as new, but then I would still have to refresh the gnus frame to
see the new messages.
Others have had this dillema and I wish I could submit a patch to fix it
but I don't have the elisp expertise. Or maybe I'm missing something?
Maybe there is a better gnus/maildir/conky setup someone else has?
--
Ben Kibbey
next parent reply other threads:[~2012-09-29 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.9955.1348869546.855.info-gnus-english@gnu.org>
2012-09-29 4:13 ` Ben Kibbey [this message]
2012-12-24 16:33 ` Lars Ingebrigtsen
2012-09-28 21:58 William Gardella
2012-09-28 23:06 ` William Gardella
2012-09-29 7:30 ` Adam Sjøgren
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=87lifteaad.fsf@luxsci.net \
--to=bjk@luxsci.net \
--cc=info-gnus-english@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).