From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ulf Stegemann Subject: Re: Store link upon sending a message Date: Fri, 01 Oct 2010 12:56:33 +0200 Message-ID: References: <87wrq29qvi.fsf@dasa3.iem.pw.edu.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from [140.186.70.92] (port=53434 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P1dII-0000Xc-Qp for emacs-orgmode@gnu.org; Fri, 01 Oct 2010 06:56:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P1dIH-0000yH-GI for emacs-orgmode@gnu.org; Fri, 01 Oct 2010 06:56:50 -0400 Received: from lo.gmane.org ([80.91.229.12]:37488) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P1dIH-0000xh-6f for emacs-orgmode@gnu.org; Fri, 01 Oct 2010 06:56:49 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1P1dI9-0002uT-VS for emacs-orgmode@gnu.org; Fri, 01 Oct 2010 12:56:41 +0200 Received: from london.zeitform.net ([146.140.213.100]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 01 Oct 2010 12:56:41 +0200 Received: from ulf-news by london.zeitform.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 01 Oct 2010 12:56:41 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Łukasz Stelmach wrote: > Ulf Stegemann writes: [snipped 15 lines] > AFAIR, message-id is used for org links rather than the articla > number. ah, right, that's at least what raw gnus-article links look like. I remember vaguely that this was different in the past and I obviously hadn't checked again. >> of the last Gcc message created. But maybe someone around here >> has a partly or completely different idea how to achieve the described >> behaviour? > > Which simplifies the problem quite a lot because we need to be able to > see the buffer just before sending or copying it to Gcc folder. All the > information is there. Yes, this makes things a lot easier :) IIUC we just need to parse the Gcc header for the group(s), grab the message-id and put things together. We should however keep in mind that we need to parse the Gcc header _before_ `gnus-inews-do-gcc' copies the message as the Gcc header is removed in the process. But the org link should probably be built _after_ `gnus-inews-do-gcc' to avoid bogus org links in case the Gcc fails. Additionally, it's probably not necessary to create a link for every group in Gcc but only for one (first one?). Furthermore, storing an org link should only happen when somehow requested by the user and not on every send. Although prefix args of `message-send' and friends already serve a different purpose that nevertheless seems to be trivial. Ulf