From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/79171 Path: news.gmane.org!not-for-mail From: lee Newsgroups: gmane.emacs.gnus.general Subject: Re: getting nndiary to work Date: Fri, 24 Jun 2011 00:21:43 +0200 Organization: my virtual residence Message-ID: <87vcvwmbns.fsf@yun.yagibdah.de> References: <87wrgdk3r0.fsf@yun.yagibdah.de> <87d3i4fnra.fsf@dod.no> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1308867780 22408 80.91.229.12 (23 Jun 2011 22:23:00 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 23 Jun 2011 22:23:00 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M27470@lists.math.uh.edu Fri Jun 24 00:22:56 2011 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 1QZsIZ-0006cn-7C for ding-account@gmane.org; Fri, 24 Jun 2011 00:22:55 +0200 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 1QZsHX-0006RM-S5; Thu, 23 Jun 2011 17:21:51 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1QZsHV-0006R4-2D for ding@lists.math.uh.edu; Thu, 23 Jun 2011 17:21:49 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1QZsHT-0006jQ-9O for ding@lists.math.uh.edu; Thu, 23 Jun 2011 17:21:48 -0500 Original-Received: from static.73.179.46.78.clients.your-server.de ([78.46.179.73]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1QZsHQ-0005La-TR for ding@gnus.org; Fri, 24 Jun 2011 00:21:44 +0200 Original-Received: from lee by yun.yagibdah.de with local (Exim 4.76) (envelope-from ) id 1QZsHP-0004AE-Cq for ding@gnus.org; Fri, 24 Jun 2011 00:21:43 +0200 Mail-Followup-To: ding@gnus.org In-Reply-To: (Didier Verna's message of "Thu, 23 Jun 2011 20:56:34 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) X-Spam-Score: 0.1 (/) X-Spam-Report: SpamAssassin (3.3.1 2010-03-16) analysis follows Bayesian score: 0.0000 Ham tokens: 0.000-1841--5930h-0s--0d--H*u:Emacs, 0.000-1711--5513h-0s--0d--H*u:Gnus, 0.000-1643--5292h-0s--0d--H*u:linux, 0.000-1643--5292h-0s--0d--H*UA:linux, 0.000-1591--5127h-0s--0d--H*u:gnu Spam tokens: 0.956-4119--1377h-51469s--0d--H*r:quimby.gnus.org, 0.925-238--192h-4027s--0d--H*r:sk:static., 0.881-1444--4082h-51749s--0d--HX-Spam-Relays-External:quimby.gnus.org, 0.881-1444--4082h-51749s--0d--H*RU:quimby.gnus.org, 0.881-1271--3683h-46391s--0d--H*Ad:D*gnus.org Autolearn status: no -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 2.0 HELO_DYNAMIC_IPADDR Relay HELO'd using suspicious hostname (IP addr 1) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:79171 Archived-At: Didier Verna writes: > Just to give you a concrete example: I receive a Call for Papers by > mail or news. What I'm doing right now is copy the message to my > [nn]diary:conferences group, and set up the X-Diary headers to the > deadline. What I would prefer to do is exactly the same, except that the > message would stay in its original group. Some things come to mind (just to give you some ideas): Save information about a message in an additional file. That could include reminder settings as well as comments. Perhaps headers could be used for such information, or headers could point to the file that holds additional information about the message. Make use of links. Gnus could create a link in an nndiary group to point to your message calling for papers. Something like that ... Use "internal" messages gnus sends itself: Instead of copying your conference message to an nndiary group, have gnus send itself a message telling it that it needs to remind you of the message calling for papers. You would just tell gnus that you want to be reminded of this particular message, and gnus transparently does whatever is needed. --- This might require introducing some sort of unique message ID for every message and ways to find messages by their unique IDs. It might get a little hairy when you have told gnus to remind you of a message and later you happen to expire the message you wanted to be reminded of ...