From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/74545 Path: news.gmane.org!not-for-mail From: Tibor Simko Newsgroups: gmane.emacs.gnus.general Subject: Re: IMAP IDLE command Date: Mon, 29 Nov 2010 22:39:32 +0100 Organization: CERN -- European Organization for Nuclear Research Message-ID: <87sjyj24iz.fsf@pcuds33.cern.ch> References: <87zkst74to.fsf@kotik.lan> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1291067118 25628 80.91.229.12 (29 Nov 2010 21:45:18 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 29 Nov 2010 21:45:18 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M22904@lists.math.uh.edu Mon Nov 29 22:45:14 2010 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PNBX6-00044A-W4 for ding-account@gmane.org; Mon, 29 Nov 2010 22:45:13 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1PNBX2-0002es-Bc; Mon, 29 Nov 2010 15:45:08 -0600 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1PNBX0-0002ec-VH for ding@lists.math.uh.edu; Mon, 29 Nov 2010 15:45:06 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtp (Exim 4.72) (envelope-from ) id 1PNBWz-0005jK-II for ding@lists.math.uh.edu; Mon, 29 Nov 2010 15:45:06 -0600 Original-Received: from lo.gmane.org ([80.91.229.12]) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1PNBWy-0001gL-00 for ; Mon, 29 Nov 2010 22:45:04 +0100 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PNBWy-00040O-PO for ding@gnus.org; Mon, 29 Nov 2010 22:45:04 +0100 Original-Received: from 52-138.77-83.cust.bluewin.ch ([83.77.138.52]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Nov 2010 22:45:04 +0100 Original-Received: from tibor.simko by 52-138.77-83.cust.bluewin.ch with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Nov 2010 22:45:04 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: ding@gnus.org Original-Lines: 50 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 52-138.77-83.cust.bluewin.ch Mail-Copies-To: never User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:OCG6N3WygaP9/AIezMD3X13A+6Q= X-Spam-Score: -1.9 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:74545 Archived-At: On Mon, 29 Nov 2010, Lars Magne Ingebrigtsen wrote: > Nope. Gnus really doesn't have any sort of mechanism for getting > updates from the servers asynchronously. But it'd be nice if it did. On a somewhat-related notification subject, and thinking of Gnus internal (non-biff) notification techniques, what is the latest state-of-the-art of gnus-notify.el and other per-article notification approaches? E.g. does new nnimap respect nnmail-read-incoming-hook or nnmail-prepare-save-mail-hook or somesuch where a per-article notification function could be plugged? A use case would go like this: instead of helping user to decide whether to do `g' (as in the case of IMAP IDLE), one would do `g' periodically anyway (e.g. via daemon), and if certain conditions are met for certain articles, notification would get displayed for each interesting article. (Could be all incoming ones, could be an interesting subset only.) To decide whether an article is interesting enough for notification, users would customize a variable say `gnus-notification-regexps' to define conditions in nnmail-split-fancy style like: (("From" "John Boss") ("From" "Jane Wife") ("To" "emergency\\.team@foo\\.com") ("Subject" "IMAP IDLE")) Hooking upon nnmail-read-incoming-hook or other some such appropriate place, if a condition is satisfied, a `gnus-notification-function' would be called, e.g. a simple notify-send call to display the sender and the subject header via a function like: (defun gnus-notification-notify-send (from subject) "Notify about new email sent by FROM on SUBJECT." (start-process "gnus-notify-send" nil "notify-send" "-i" "/usr/share/pixmaps/gnome-emacs.png" (format "New email from %s" from) (format "Subject: %s" subject))) Would such a notification system be of general interest to have in Gnus? It would basically only help users to decide whether to open certain groups or not; though it could also serve for `quick-scanning' of activity in some shared IMAP groups, in case several people have access to the same IMAP account, for example. (Though an external real-time biffer may be better suited for this.) WDYT? Best regards -- Tibor Simko