From f153f48bcaab5725843ef4ca8226322b711aec83 Mon Sep 17 00:00:00 2001 From: David Edmondson Date: Wed, 29 Oct 2014 13:41:44 +0000 Subject: [PATCH] Re: [O] how to put into a journal info about the email sent --- b5/d60e44586c4a777b30ebe825b840c1fe72294d | 104 ++++++++++++++++++++++ 1 file changed, 104 insertions(+) create mode 100644 b5/d60e44586c4a777b30ebe825b840c1fe72294d diff --git a/b5/d60e44586c4a777b30ebe825b840c1fe72294d b/b5/d60e44586c4a777b30ebe825b840c1fe72294d new file mode 100644 index 000000000..8d5172899 --- /dev/null +++ b/b5/d60e44586c4a777b30ebe825b840c1fe72294d @@ -0,0 +1,104 @@ +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 C47AA431FC2 + for ; Wed, 29 Oct 2014 06:41:55 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -0.699 +X-Spam-Level: +X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 + tests=[RCVD_IN_DNSWL_LOW=-0.7, UNPARSEABLE_RELAY=0.001] + 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 JyQwHDRu+lCo for ; + Wed, 29 Oct 2014 06:41:50 -0700 (PDT) +Received: from mail-wg0-f45.google.com (mail-wg0-f45.google.com + [74.125.82.45]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client + certificate requested) by olra.theworths.org (Postfix) with ESMTPS id + 241CE431FB6 for ; Wed, 29 Oct 2014 06:41:50 -0700 + (PDT) +Received: by mail-wg0-f45.google.com with SMTP id x12so1929498wgg.18 + for ; Wed, 29 Oct 2014 06:41:48 -0700 (PDT) +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=1e100.net; s=20130820; + h=x-gm-message-state:to:cc:subject:in-reply-to:references:user-agent + :from:date:message-id:mime-version:content-type; + bh=qpnRY3K1LhWrIUprRkaGIjO7FC3QZFMuDvCJjrW4aNg=; + b=ZNVFHewuLNrSCF+7IWDKt74b+YXfdvA5Uw6VQJKxTE4mkUXlZPYC2gc1YQlNdX5nHW + 23HnSzqTHyr2KBT9IukZ1nAUbicWWBUfAMjPU6rsZqHG4Baaf5eVm2B0GJDdc8rbWcim + Ot4bqQiC180JJRi+FOOwdj1tDo+foQ3i0e43a/lsbJEWwH1OqcDrI5qRX2pBYcTnFzYn + WE/fIB9CQUz82d56ji5fWuEYHDjLJjlsya0iZ1zt1J7tkIJ3/uCj25DRaoEHn2Ub0VWw + uXYyzSFiRnPwTVNBGR2zpixFK2YrZO4/1toeqFNkUQI9ByrTU1QejenYawaIFTzti5ee + Hkog== +X-Gm-Message-State: + ALoCoQnLvdcPSYthEdsPpxnIz3vJ2gbLJL6U7S+imxDcMSLNQ3tcvNTxxi4ej3JumyKbqdJYZgO8 +X-Received: by 10.180.9.169 with SMTP id a9mr12805951wib.7.1414590107595; + Wed, 29 Oct 2014 06:41:47 -0700 (PDT) +Received: from disaster-area.hh.sledj.net + ([2a01:348:1a2:1:ea39:35ff:fe2c:a227]) + by mx.google.com with ESMTPSA id fa7sm5232839wjd.27.2014.10.29.06.41.46 + for + (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); + Wed, 29 Oct 2014 06:41:46 -0700 (PDT) +Received: from localhost (30000@localhost [local]); + by localhost (OpenSMTPD) with ESMTPA id 66843030; + Wed, 29 Oct 2014 13:41:45 +0000 (UTC) +To: David Belohrad , + 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.1 (http://notmuchmail.org) Emacs/24.3.1 + (x86_64-pc-linux-gnu) +From: David Edmondson +Date: Wed, 29 Oct 2014 13:41:44 +0000 +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:41:55 -0000 + +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. -- 2.26.2