emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric-5ibeKGLO59aIK5dEoMBc7KxOck334EZe@public.gmane.org>
To: notmuch-gxuj+Tv9EO5zyzON3hdc1g@public.gmane.org
Cc: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: how to put into a journal info about the email sent
Date: Fri, 24 Oct 2014 10:02:10 -0700	[thread overview]
Message-ID: <87a94lh04t.fsf@ericabrahamsen.net> (raw)
In-Reply-To: m2k33p31yb.fsf@heart-of-gold.hh.sledj.net

David Edmondson <dme-zDQXUQW/Few@public.gmane.org> writes:

> On Fri, Oct 24 2014, Eric Abrahamsen wrote:
>> David Belohrad <david-rZamiVn3bvgfv37vnLkPlQ@public.gmane.org> 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.

  reply	other threads:[~2014-10-24 17:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 14:36 how to put into a journal info about the email sent David Belohrad
2014-10-24 15:43 ` Eric Abrahamsen
     [not found]   ` <87ppdhh3rh.fsf-5ibeKGLO59aIK5dEoMBc7KxOck334EZe@public.gmane.org>
2014-10-24 15:46     ` David Edmondson
2014-10-24 17:02       ` Eric Abrahamsen [this message]
     [not found]         ` <87a94lh04t.fsf-5ibeKGLO59aIK5dEoMBc7KxOck334EZe@public.gmane.org>
2014-10-29 13:09           ` David Belohrad
     [not found]             ` <uaxd29bt43r.fsf-l29r6ovuLp4041QeWSbL1u1GAupnlqi7@public.gmane.org>
2014-10-29 13:41               ` David Edmondson
     [not found]                 ` <cuny4rzngbr.fsf-cKoGAlAyRl4B6mVx8Gbmpr8CxMaF4oN5@public.gmane.org>
2014-10-29 13:49                   ` David Belohrad

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a94lh04t.fsf@ericabrahamsen.net \
    --to=eric-5ibekglo59aik5deombc7kxock334eze@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    --cc=notmuch-gxuj+Tv9EO5zyzON3hdc1g@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).