From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Belohrad Subject: Re: how to put into a journal info about the email sent Date: Wed, 29 Oct 2014 14:49:24 +0100 Message-ID: References: <87ppdhh3rh.fsf@ericabrahamsen.net> <87a94lh04t.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: notmuch-bounces-gxuj+Tv9EO5zyzON3hdc1g@public.gmane.org Errors-To: notmuch-bounces-gxuj+Tv9EO5zyzON3hdc1g@public.gmane.org To: David Edmondson , Eric Abrahamsen , notmuch-gxuj+Tv9EO5zyzON3hdc1g@public.gmane.org Cc: emacs-orgmode-mXXj517/zsQ@public.gmane.org List-Id: emacs-orgmode.gnu.org 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.