1 Return-Path: <gmn-notmuch@m.gmane.org>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 1268A431FC9
\r
6 for <notmuch@notmuchmail.org>; Fri, 24 Oct 2014 09:57:36 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id DySEMYR1VxBb for <notmuch@notmuchmail.org>;
\r
16 Fri, 24 Oct 2014 09:57:28 -0700 (PDT)
\r
17 Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
\r
18 (using TLSv1 with cipher AES256-SHA (256/256 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id 21697431FBD
\r
21 for <notmuch@notmuchmail.org>; Fri, 24 Oct 2014 09:57:28 -0700 (PDT)
\r
22 Received: from list by plane.gmane.org with local (Exim 4.69)
\r
23 (envelope-from <gmn-notmuch@m.gmane.org>) id 1XhiB0-0004wn-QL
\r
24 for notmuch@notmuchmail.org; Fri, 24 Oct 2014 18:57:22 +0200
\r
25 Received: from c-76-28-195-250.hsd1.wa.comcast.net ([76.28.195.250])
\r
26 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
\r
28 for <notmuch@notmuchmail.org>; Fri, 24 Oct 2014 18:57:22 +0200
\r
29 Received: from eric by c-76-28-195-250.hsd1.wa.comcast.net with local (Gmexim
\r
30 0.1 (Debian)) id 1AlnuQ-0007hv-00
\r
31 for <notmuch@notmuchmail.org>; Fri, 24 Oct 2014 18:57:22 +0200
\r
32 X-Injected-Via-Gmane: http://gmane.org/
\r
33 To: notmuch@notmuchmail.org
\r
34 From: Eric Abrahamsen <eric@ericabrahamsen.net>
\r
35 Subject: Re: [O] how to put into a journal info about the email sent
\r
36 Followup-To: gmane.emacs.orgmode
\r
37 Date: Fri, 24 Oct 2014 10:02:10 -0700
\r
39 Message-ID: <87a94lh04t.fsf@ericabrahamsen.net>
\r
40 References: <uaxh9yty1pm.fsf@beesknees.cern.ch>
\r
41 <87ppdhh3rh.fsf@ericabrahamsen.net>
\r
42 <m2k33p31yb.fsf@heart-of-gold.hh.sledj.net>
\r
44 Content-Type: text/plain
\r
45 X-Complaints-To: usenet@ger.gmane.org
\r
46 X-Gmane-NNTP-Posting-Host: c-76-28-195-250.hsd1.wa.comcast.net
\r
47 User-Agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/25.0.50 (gnu/linux)
\r
48 Cancel-Lock: sha1:IPoQ6Jh7S/3SC/8FCtzXMQSKkh8=
\r
49 Cc: emacs-orgmode@gnu.org
\r
50 X-BeenThere: notmuch@notmuchmail.org
\r
51 X-Mailman-Version: 2.1.13
\r
53 List-Id: "Use and development of the notmuch mail system."
\r
54 <notmuch.notmuchmail.org>
\r
55 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
56 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
57 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
58 List-Post: <mailto:notmuch@notmuchmail.org>
\r
59 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
60 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
61 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
62 X-List-Received-Date: Fri, 24 Oct 2014 16:57:36 -0000
\r
64 David Edmondson <dme@dme.org> writes:
\r
66 > On Fri, Oct 24 2014, Eric Abrahamsen wrote:
\r
67 >> David Belohrad <david@belohrad.ch> writes:
\r
71 >>> i'm using org. And I'm using notmuch (that's why I address both mailing
\r
72 >>> lists). Now, writing an email in everyday bussiness requires a
\r
73 >>> non-significant time of your workhours. So I'd like to have this event
\r
74 >>> in my org agenda. So any time I send some email with a given subject,
\r
75 >>> I'd like to 'automatically' entry the information about it into
\r
76 >>> e.g. sentmails.org in form of a diary entry, with appropriate tag.
\r
78 >> I do something like this in Gnorb, which I'd recommend you use except
\r
79 >> it's mostly Gnus specific.
\r
81 >> I do it in two parts, but you could do it in one. Basically I add a
\r
82 >> function to the `message-header-hook' (which ensures that all the
\r
83 >> message headers have been generated properly).
\r
85 > Does `message-generate-headers-first' not do what you want for this
\r
88 Yeah, I think I looked at that previously. But this thing is going in a
\r
89 hook anyway, might as well use the hook that *doesn't* require me to
\r
90 call that function explicitly.
\r
92 >> Obviously the downside is that, without a "Gcc:" header, org can't
\r
93 >> actually make a real link to the message. It doesn't know where it's
\r
94 >> going to be. However if you know that all your sent messages can be
\r
95 >> reached with a link that looks like "notmuch:id#Message-id", then you
\r
96 >> can make that yourself in your org capture template with something like
\r
98 > As you suggest, know the message-id should be good enough to generate a
\r
99 > notmuch link, though you may have to wait for the notmuch index to be
\r
100 > updated for the link to be valid.
\r
102 Yup, I've got the same issue with nnimap -- you have to wait for the
\r
103 next sync to get access to the message. So far it hasn't been a problem,
\r