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 9B75F431FC2 for ; Wed, 29 Oct 2014 06:49:35 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] 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 i119DM12FGzS for ; Wed, 29 Oct 2014 06:49:27 -0700 (PDT) Received: from beesknees.cern.ch (beesknees.cern.ch [137.138.197.99]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 8AFB2431FB6 for ; Wed, 29 Oct 2014 06:49:27 -0700 (PDT) Received: from belohrad by beesknees.cern.ch with local (Exim 4.84) (envelope-from ) id 1XjTcq-0003iq-V6; Wed, 29 Oct 2014 14:49:25 +0100 From: David Belohrad To: David Edmondson , Eric Abrahamsen , notmuch@notmuchmail.org Subject: Re: [O] how to put into a journal info about the email sent In-Reply-To: References: <87ppdhh3rh.fsf@ericabrahamsen.net> <87a94lh04t.fsf@ericabrahamsen.net> User-Agent: Notmuch/0.18~rc0+2~gbc64cdc (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Wed, 29 Oct 2014 14:49:24 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain 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: Wed, 29 Oct 2014 13:49:35 -0000 Hi David, yes. That works perfectly and solves both issues at the same time. Now it is perfect! .d. David Edmondson writes: > On Wed, Oct 29 2014, David Belohrad wrote: >> - 'standard' behaviour is, that the email sent becomes read-only so with >> 'q' keystroke I can bury the buffer with the email. However when I >> have implemented this, I have noticed that when I 'confirm' the >> template, I go back into the buffer 'sent mail to...', but this the >> *THE BUFFER IS NOT READ ONLY* and 'q' will just generate a character, >> and then I have to kill this buffer using C-x k with additional 'yes' >> because the buffer was modified. Quite annoying and I don't know how >> to resolve this > > I'm unsure about this. The change below may fix it accidentally. > >> - second thing is, that I'd like to avoid at all opening the capture >> template and just dump it into the file without any modifications >> ongoing. The only 'modification' which comes into my mind is a setup >> of an additional tag describing the email being attached to some >> project... > > Change the template to... > > ("@" "Email outgoing sync. USED INTERNALLY" entry (file+datetree (concat my-org-files "emails_sent.org")) > "* EMAIL %c :EMAIL:\n%?\nEntered on %T\n" :immediate-finish t) > (i.e. add ":immediate-finish t") > > ...and you will never see the capture buffer for this entry.