Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@googlemail.com>
To: info-gnus-english@gnu.org
Subject: Re: Gnus and new mail notification
Date: Sat, 25 Dec 2010 21:31:43 +0100	[thread overview]
Message-ID: <if5kbf$8fh$1@quimby.gnus.org> (raw)
In-Reply-To: <mailman.26.1293233609.7272.info-gnus-english@gnu.org>

Yuri D'Elia <wavexx@users.sf.net> writes:

> I wasn't happy with the existing new mail notification scripts that I've
> found on emacswiki.
>
> I've put together a new script, called "gnus-notify"[1], that can call
> any arbitrary program when new messages are received. The default uses
> the 'notify-send' program (part of libnotify's library) which creates
> little popup messages. This is especially useful if you have virtual
> desktops and leave Gnus running with gnus-demon.
>
> The result (showing Gnus + awesomewm + libnotify-bin on Debian) is shown
> here:
>
>   http://www.thregr.org/~wavexx/hacks/gnus-notify.png
>
> You can also do arbitrary stuff by either setting a different
> executable, or supplying an entirely new notification function.
> Simply read the commentary in the source.
>
> gnus-notify.el is available at:
>
>   http://www.thregr.org/~wavexx/hacks/gnus-notify.el
>
> Merry christmas :)
>
> [1] I know there's already a gnus-notify.el script, but I wasn't able to
>     come up with a better name.
>

I'm interested how this helps - I think I'm missing something. Since
this can only work in Gnus when Gnus sees new mail what purpose does it
server since Gnus has already fetched the mail : isnt a third party
imap/maildir asynchronous monitor a better solution for this external
notification process?

Also using the same name is somewhat silly since it will clash if
packaged in ELPA or something especially as it does something totally
different to gnus-notify : what about gnus-external-notify?

regards

r.

  parent reply	other threads:[~2010-12-25 20:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.26.1293233609.7272.info-gnus-english@gnu.org>
2010-12-25 13:25 ` e20100633
2010-12-26 18:26   ` Philipp Haselwarter
2010-12-26 18:59     ` Philipp Haselwarter
2010-12-25 20:31 ` Richard Riley [this message]
2010-12-25 21:55   ` Tassilo Horn
2010-12-25 22:56   ` Yuri D'Elia
     [not found]   ` <mailman.13.1293317806.24913.info-gnus-english@gnu.org>
2010-12-25 23:19     ` Richard Riley
2010-12-26 16:22       ` Yuri D'Elia
     [not found]       ` <mailman.1.1293380566.6185.info-gnus-english@gnu.org>
2010-12-27  8:11         ` Richard Riley
2010-12-27  9:25           ` Thierry Volpiatto
     [not found]           ` <mailman.2.1293441979.18751.info-gnus-english@gnu.org>
2010-12-27 13:30             ` Richard Riley
2010-12-27 15:39               ` Philipp Haselwarter
2010-12-27 16:04               ` Thierry Volpiatto
     [not found]               ` <mailman.8.1293465927.24495.info-gnus-english@gnu.org>
2010-12-27 16:42                 ` Richard Riley
2010-12-27 17:47                   ` Thierry Volpiatto
     [not found]                   ` <mailman.19.1293472126.24495.info-gnus-english@gnu.org>
2010-12-27 18:11                     ` Richard Riley
2010-12-27 19:09                       ` Thierry Volpiatto
2010-12-24 23:33 Yuri D'Elia
2010-12-25 13:10 ` Philipp Haselwarter
2010-12-25 15:26   ` Yuri D'Elia
2010-12-25 21:52     ` Tassilo Horn
2010-12-26 20:11 ` Yuri D'Elia
2011-01-02 12:02   ` Philipp Haselwarter

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='if5kbf$8fh$1@quimby.gnus.org' \
    --to=rileyrg@googlemail.com \
    --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).