From: Mykola Nikishov <mn@mn.com.ua>
To: emacs-orgmode@gnu.org
Subject: Re: keeping track of sent emails in org?
Date: Wed, 29 Oct 2008 16:08:19 +0200 [thread overview]
Message-ID: <87prlj8pf0.fsf@tabernacle.mn.home> (raw)
In-Reply-To: 78FE502B-5C3D-4B7C-96FE-40AC2E17E19B@uva.nl
Carsten Dominik <dominik@science.uva.nl> writes:
> In the git version, message ids are now used for links to gnus articles.
> Could some of you please verify this change?
diff --git a/GettingThingsDone/MyLife.org b/GettingThingsDone/MyLife.org
index 6fb33be..806c779 100644
--- a/GettingThingsDone/MyLife.org
+++ b/GettingThingsDone/MyLife.org
@@ -106,8 +106,8 @@ analyze.
* TODO [#A] review
SCHEDULED: <2008-11-21 пт>
[2008-09-22 Mon 17:50]
-[[gnus:nnmaildir%2Blocalhost:inbox#13179][Email from Lyudmyla]]
-[[gnus:nnmaildir%2Blocalhost:bogofilter-unsure#1139][Email from Volodymyr]]
+[[gnus:nnvirtual:inboxes#<74ED9393FA836744B9309ED04DC6725517FEB5@EX2-KBP1.synapse.com][Email from Lyudmyla
+[[gnus:nnmaildir%2Blocalhost:inbox#<05D3ECB61D5F76479E5C33D99AB628F8A01D5C@EX2-KBP1.synapse.com][Email from Vo
* TODO try [[deb:solfege]]
:PROPERTIES:
:CATEGORY: debian
With org's revision 17c55f1b I can open linked messages with 'C-c C-o'
when in org file. But I need more time to investigate two use cases:
- message was moved into other group with 'B m'
- gnus is not running when C-c C-o pressed
> Thanks to Ross and Michael for input, I looked at their code to
> implement this.
+1
--
MAN-UANIC
next prev parent reply other threads:[~2008-10-29 15:08 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
2008-10-29 17:41 ` Ross Patterson
2008-10-29 14:08 ` Mykola Nikishov [this message]
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=87prlj8pf0.fsf@tabernacle.mn.home \
--to=mn@mn.com.ua \
--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).