Re: [O] how to put into a journal info about the email sent

diff --git a/6e/3ea44f0da69083987604c9c0f6028060680a4e b/6e/3ea44f0da69083987604c9c0f6028060680a4e
new file mode 100644 (file)
index 0000000..669b132
--- /dev/null
+++ b/6e/3ea44f0da69083987604c9c0f6028060680a4e
@@ -0,0 +1,92 @@
+Return-Path: <david@belohrad.ch>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 9B75F431FC2\r
+       for <notmuch@notmuchmail.org>; Wed, 29 Oct 2014 06:49:35 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id i119DM12FGzS for <notmuch@notmuchmail.org>;\r
+       Wed, 29 Oct 2014 06:49:27 -0700 (PDT)\r
+Received: from beesknees.cern.ch (beesknees.cern.ch [137.138.197.99])\r
+       (using TLSv1 with cipher AES128-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 8AFB2431FB6\r
+       for <notmuch@notmuchmail.org>; Wed, 29 Oct 2014 06:49:27 -0700 (PDT)\r
+Received: from belohrad by beesknees.cern.ch with local (Exim 4.84)\r
+       (envelope-from <david@belohrad.ch>)\r
+       id 1XjTcq-0003iq-V6; Wed, 29 Oct 2014 14:49:25 +0100\r
+From: David Belohrad <david@belohrad.ch>\r
+To: David Edmondson <dme@dme.org>, Eric Abrahamsen <eric@ericabrahamsen.net>,\r
+       notmuch@notmuchmail.org\r
+Subject: Re: [O] how to put into a journal info about the email sent\r
+In-Reply-To: <cuny4rzngbr.fsf@gargravarr.hh.sledj.net>\r
+References: <uaxh9yty1pm.fsf@beesknees.cern.ch>\r
+       <87ppdhh3rh.fsf@ericabrahamsen.net>\r
+       <m2k33p31yb.fsf@heart-of-gold.hh.sledj.net>\r
+       <87a94lh04t.fsf@ericabrahamsen.net>\r
+       <uaxd29bt43r.fsf@beesknees.cern.ch>\r
+       <cuny4rzngbr.fsf@gargravarr.hh.sledj.net>\r
+User-Agent: Notmuch/0.18~rc0+2~gbc64cdc (http://notmuchmail.org) Emacs/24.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Wed, 29 Oct 2014 14:49:24 +0100\r
+Message-ID: <uaxsii7rnob.fsf@beesknees.cern.ch>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+Cc: emacs-orgmode@gnu.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 29 Oct 2014 13:49:35 -0000\r
+\r
+Hi David,\r
+\r
+yes. That works perfectly and solves both issues at the same time. Now\r
+it is perfect!\r
+\r
+.d.\r
+\r
+\r
+\r
+David Edmondson <dme@dme.org> writes:\r
+\r
+> On Wed, Oct 29 2014, David Belohrad wrote:\r
+>> - 'standard' behaviour is, that the email sent becomes read-only so with\r
+>>   'q' keystroke I can bury the buffer with the email. However when I\r
+>>   have implemented this, I have noticed that when I 'confirm' the\r
+>>   template, I go back into the buffer 'sent mail to...', but this the\r
+>>   *THE BUFFER IS NOT READ ONLY* and 'q' will just generate a character,\r
+>>   and then I have to kill this buffer using C-x k with additional 'yes'\r
+>>   because the buffer was modified. Quite annoying and I don't know how\r
+>>   to resolve this\r
+>\r
+> I'm unsure about this. The change below may fix it accidentally.\r
+>\r
+>> - second thing is, that I'd like to avoid at all opening the capture\r
+>>   template and just dump it into the file without any modifications\r
+>>   ongoing. The only 'modification' which comes into my mind is a setup\r
+>>   of an additional tag describing the email being attached to some\r
+>>   project...\r
+>\r
+> Change the template to...\r
+>\r
+>     ("@" "Email outgoing sync. USED INTERNALLY" entry (file+datetree (concat my-org-files "emails_sent.org"))\r
+>     "* EMAIL %c :EMAIL:\n%?\nEntered on %T\n" :immediate-finish t)\r
+> (i.e. add ":immediate-finish t")\r
+>\r
+> ...and you will never see the capture buffer for this entry.\r