From: Christopher Suckling <suckling.list@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Re: keeping track of sent emails in org?
Date: Wed, 29 Oct 2008 08:06:28 -0700 [thread overview]
Message-ID: <20081029150628.GB1759@rushka.local> (raw)
In-Reply-To: <87zlknk0r6.fsf@katana.lair>
On Wed, Oct 29, 2008 at 02:07:57PM +0100, Georg C. F. Greve wrote:
>
> I just saw this thread and believe that
>
> http://www.emacswiki.org/emacs/org-mairix.el
>
> might contain parts of the answer, at least. I've been trying to come up
> with a better solution, and kept meaning to come back to it, but haven't
> managed thus far.
>
> The fundamental problem of getting the message ID, which is sufficient
> for linking to an article through mairix search has been solved, though.
>
For the very few people who use OS X, mutt, Quicksilver and org-mode,
I've got a solution to this at
http://claviclaws.net/org/
I use Quicksilver to trigger an AppleScript which send a key command
to mutt, triggering the following macro:
macro index,pager "I" "<pipe-message>/usr/bin/formail -X Message-ID -X
Subject | cut -d\">\" -f1 | tr -d \"<\" |
~/.mutt/org-mairix-link.sh\n"
This uses formail to pass the Message-ID and Subject to a shell script
(available at above site) which in turn formats an org-mairix link and
sends it to the Emacs kill-ring.
Hope this might be of some use,
Christopher
next prev parent reply other threads:[~2008-10-29 15:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 17:31 keeping track of sent emails in org? Bill White
2008-10-27 14:20 ` Sebastian Rose
2008-10-27 15:01 ` Sebastian Rose
2008-10-27 18:11 ` Eric Schulte
2008-10-27 21:17 ` Bill White
2008-10-27 21:31 ` Chris McMahan
2008-10-27 21:35 ` Carsten Dominik
2008-10-27 21:45 ` Richard Riley
2008-10-27 21:49 ` Bill White
2008-10-27 21:59 ` Carsten Dominik
2008-10-27 22:43 ` Bill White
2008-10-27 23:12 ` Michael Ekstrand
2008-10-28 1:35 ` Michael Ekstrand
2008-11-03 11:18 ` Carsten Dominik
2008-11-03 13:37 ` Michael Ekstrand
2008-10-29 8:56 ` Carsten Dominik
2008-10-29 12:21 ` Sebastian Rose
2008-10-29 11:27 ` Pete Phillips
2008-10-29 12:37 ` Carsten Dominik
2008-10-29 13:07 ` Georg C. F. Greve
2008-10-29 15:06 ` Christopher Suckling [this message]
2008-10-29 17:41 ` Ross Patterson
2008-10-29 14:08 ` Mykola Nikishov
2008-10-29 15:17 ` Bernt Hansen
2008-10-29 15:44 ` Carsten Dominik
2008-10-29 15:47 ` Bernt Hansen
2008-10-29 16:08 ` Bernt Hansen
2008-10-29 17:39 ` Ross Patterson
2008-10-29 18:03 ` Bernt Hansen
2008-10-29 18:08 ` Ross Patterson
2008-10-27 21:06 ` Bill White
2008-10-28 17:58 ` Carsten Dominik
2008-10-28 18:46 ` Ross Patterson
2008-10-28 19:14 ` Carsten Dominik
2008-10-28 19:19 ` Ross Patterson
2008-10-29 8:17 ` Carsten Dominik
2008-10-28 20:14 ` Bill White
-- strict thread matches above, loose matches on Subject: below --
2008-10-28 20:37 Sullivan, Gregory (US SSA)
2008-10-29 9:38 ` Pete Phillips
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=20081029150628.GB1759@rushka.local \
--to=suckling.list@googlemail.com \
--cc=emacs-orgmode@gnu.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).