Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: wgreenhouse-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org (W. Greenhouse)
To: info-gnus-english-mXXj517/zsQ@public.gmane.org
Subject: Re: Gnus state, feed commands
Date: Wed, 20 Nov 2013 23:00:37 +0000	[thread overview]
Message-ID: <87mwkyisq2.fsf@motoko.kusanagi> (raw)
In-Reply-To: <8761rq4m3u.fsf@nl106-137-194.student.uu.se>

Emanuel Berg <embe8573-oe7qfRrRQfc4M/bo5TPICw@public.gmane.org> writes:

> I "sort of" solved this. Check out the comments.

[...]


Cool.

An alternate approach to the problem: track the place Gnus is getting
its mail from.  `display-time-mode' has some built-in support for this.

My MTA delivers new mails for me to a Maildir at ~/Maildir, so with

(setq display-time-mail-directory "~/Maildir/new/") 

I can get "Mail" in my mode line when display-time-mode is on and mail
arrives at ~/Maildir.  In the Maildir format, the new/ subdir is where
mails arrive; when Gnus processes them, whether by marking them unread
or flagged or splitting them to other folders, they are moved to cur/,
so new/ will only contain new, unprocessed mail.

There are also options to use an mbox file or an arbitrary function to
test for the rpesence of new mail every time `display-time' updates.  If
you use Gnus `mail-sources' to control where your mail comes from, you
might try

(setq display-time-mail-function 'mail-source-new-mail-p)

  reply	other threads:[~2013-11-20 23:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-16 18:17 Emanuel Berg
2013-11-16 19:31 ` W. Greenhouse
     [not found] ` <mailman.6381.1384630484.10748.info-gnus-english@gnu.org>
2013-11-16 20:03   ` Emanuel Berg
2013-11-17 23:57     ` Emanuel Berg
2013-11-20 23:00       ` W. Greenhouse [this message]
     [not found]       ` <mailman.6725.1384988464.10748.info-gnus-english@gnu.org>
2013-11-21 22:54         ` Emanuel Berg

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=87mwkyisq2.fsf@motoko.kusanagi \
    --to=wgreenhouse-sgozh3hwpm2stnjn9+bgxg@public.gmane.org \
    --cc=info-gnus-english-mXXj517/zsQ@public.gmane.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).