From: Eric Abrahamsen Date: Fri, 24 Oct 2014 17:02:10 +0000 (+1700) Subject: Re: [O] how to put into a journal info about the email sent X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=ed97014ff52d7c794168693fc98892732d0bc4ef;p=notmuch-archives.git Re: [O] how to put into a journal info about the email sent --- diff --git a/4b/5daf9e28754fbf9a521c5db820b2a4edb6646a b/4b/5daf9e28754fbf9a521c5db820b2a4edb6646a new file mode 100644 index 000000000..cf929fd98 --- /dev/null +++ b/4b/5daf9e28754fbf9a521c5db820b2a4edb6646a @@ -0,0 +1,105 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id 1268A431FC9 + for ; Fri, 24 Oct 2014 09:57:36 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -0.7 +X-Spam-Level: +X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 + tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id DySEMYR1VxBb for ; + Fri, 24 Oct 2014 09:57:28 -0700 (PDT) +Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) + (using TLSv1 with cipher AES256-SHA (256/256 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id 21697431FBD + for ; Fri, 24 Oct 2014 09:57:28 -0700 (PDT) +Received: from list by plane.gmane.org with local (Exim 4.69) + (envelope-from ) id 1XhiB0-0004wn-QL + for notmuch@notmuchmail.org; Fri, 24 Oct 2014 18:57:22 +0200 +Received: from c-76-28-195-250.hsd1.wa.comcast.net ([76.28.195.250]) + by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) + id 1AlnuQ-0007hv-00 + for ; Fri, 24 Oct 2014 18:57:22 +0200 +Received: from eric by c-76-28-195-250.hsd1.wa.comcast.net with local (Gmexim + 0.1 (Debian)) id 1AlnuQ-0007hv-00 + for ; Fri, 24 Oct 2014 18:57:22 +0200 +X-Injected-Via-Gmane: http://gmane.org/ +To: notmuch@notmuchmail.org +From: Eric Abrahamsen +Subject: Re: [O] how to put into a journal info about the email sent +Followup-To: gmane.emacs.orgmode +Date: Fri, 24 Oct 2014 10:02:10 -0700 +Lines: 41 +Message-ID: <87a94lh04t.fsf@ericabrahamsen.net> +References: + <87ppdhh3rh.fsf@ericabrahamsen.net> + +Mime-Version: 1.0 +Content-Type: text/plain +X-Complaints-To: usenet@ger.gmane.org +X-Gmane-NNTP-Posting-Host: c-76-28-195-250.hsd1.wa.comcast.net +User-Agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/25.0.50 (gnu/linux) +Cancel-Lock: sha1:IPoQ6Jh7S/3SC/8FCtzXMQSKkh8= +Cc: emacs-orgmode@gnu.org +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +Precedence: list +List-Id: "Use and development of the notmuch mail system." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Fri, 24 Oct 2014 16:57:36 -0000 + +David Edmondson writes: + +> On Fri, Oct 24 2014, Eric Abrahamsen wrote: +>> David Belohrad writes: +>> +>>> Dear All, +>>> +>>> i'm using org. And I'm using notmuch (that's why I address both mailing +>>> lists). Now, writing an email in everyday bussiness requires a +>>> non-significant time of your workhours. So I'd like to have this event +>>> in my org agenda. So any time I send some email with a given subject, +>>> I'd like to 'automatically' entry the information about it into +>>> e.g. sentmails.org in form of a diary entry, with appropriate tag. +>> +>> I do something like this in Gnorb, which I'd recommend you use except +>> it's mostly Gnus specific. +>> +>> I do it in two parts, but you could do it in one. Basically I add a +>> function to the `message-header-hook' (which ensures that all the +>> message headers have been generated properly). +> +> Does `message-generate-headers-first' not do what you want for this +> specific part? + +Yeah, I think I looked at that previously. But this thing is going in a +hook anyway, might as well use the hook that *doesn't* require me to +call that function explicitly. + +>> Obviously the downside is that, without a "Gcc:" header, org can't +>> actually make a real link to the message. It doesn't know where it's +>> going to be. However if you know that all your sent messages can be +>> reached with a link that looks like "notmuch:id#Message-id", then you +>> can make that yourself in your org capture template with something like +> +> As you suggest, know the message-id should be good enough to generate a +> notmuch link, though you may have to wait for the notmuch index to be +> updated for the link to be valid. + +Yup, I've got the same issue with nnimap -- you have to wait for the +next sync to get access to the message. So far it hasn't been a problem, +though. +