From: Dan Christensen <jdc@uwo.ca>
To: emacs-orgmode@gnu.org
Cc: ding@gnus.org
Subject: Re: org-mode gnus integration across two machines when using nnimap
Date: Fri, 26 Nov 2010 14:40:18 -0500 [thread overview]
Message-ID: <87hbf3yiu5.fsf@uwo.ca> (raw)
In-Reply-To: <m262vj3oij.fsf@verilab.com>
Tommy Kelly <tommy.kelly@verilab.com> writes:
> Here's the link to your reply to me:
>
> [[gnus:gmane.emacs.gnus.general#87tyj4x798.fsf@uwo.ca][Email from Dan Christensen: Re: org-mode gnus integration ]]
Since this stores the group name and the message-id, it should work across
different Gnus sessions.
> The reason I assumed there would be a problem is that even if I simply
> *move* a Gnus article from one group to another, that breaks the
> link.
That makes sense, since the link refers to the group.
I believe the Gnus registry can keep track of the message ID --> group
mapping, so org-mode could use this if the article isn't found in the
expected group and the user has the registry enabled.
I don't use org-mode or the registry, so I'll let others respond if
there are further questions.
Dan
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-11-26 19:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <icon35$qaq$1@dough.gmane.org>
[not found] ` <FBA00F24-6991-4305-918C-FBE06BC011CA@gmail.com>
2010-11-26 18:20 ` Tommy Kelly
2010-11-26 18:35 ` Dan Christensen
2010-11-26 18:53 ` Tommy Kelly
2010-11-26 19:40 ` Dan Christensen [this message]
2010-12-14 23:07 ` Ted Zlatanov
2010-12-01 18:41 ` e20100633
2010-12-01 22:55 ` [Orgmode] " Eric S Fraga
2010-12-01 23:44 ` e20100633
2010-12-02 1:32 ` Bernt Hansen
2010-12-02 7:24 ` e20100633
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hbf3yiu5.fsf@uwo.ca \
--to=jdc@uwo.ca \
--cc=ding@gnus.org \
--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.
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 NNTP newsgroup(s).