From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode gnus integration across two machines when using nnimap
Date: Tue, 14 Dec 2010 17:07:22 -0600 [thread overview]
Message-ID: <87pqt4lzrp.fsf@lifelogs.com> (raw)
In-Reply-To: 87hbf3yiu5.fsf@uwo.ca
On Fri, 26 Nov 2010 14:40:18 -0500 Dan Christensen <jdc@uwo.ca> wrote:
DC> 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 ]]
DC> Since this stores the group name and the message-id, it should work across
DC> 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.
DC> That makes sense, since the link refers to the group.
DC> I believe the Gnus registry can keep track of the message ID --> group
DC> mapping, so org-mode could use this if the article isn't found in the
DC> expected group and the user has the registry enabled.
Yes, but it can fail (it doesn't catch external moves and the user can
limit the registry size to save memory). See nnregistry.el for an
example of how to use `gnus-refer-article-method' with the registry. So
maybe the org-mode Gnus integration can use gnus-refer-article-method,
if it doesn't already, and let the user decide if the registry should be
part of the refer search path.
Ted
next prev parent reply other threads:[~2010-12-14 23:07 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 16:26 moving in the agenda view is slow Rainer Stengele
2010-11-26 16:46 ` Carsten Dominik
2010-11-26 18:20 ` org-mode gnus integration across two machines when using nnimap Tommy Kelly
2010-11-26 18:35 ` Dan Christensen
2010-11-26 18:53 ` Tommy Kelly
2010-11-26 19:40 ` Dan Christensen
2010-12-14 23:07 ` Ted Zlatanov [this message]
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
2010-12-02 1:55 ` Greg Troxel
2010-12-02 2:58 ` Matt Lundin
2010-11-26 20:15 ` moving in the agenda view is slow Martin Stemplinger
2010-11-26 21:28 ` Markus Heller
2010-11-27 11:31 ` Rainer Stengele
2010-11-26 23:04 ` Eric S Fraga
2010-11-26 23:08 ` Carsten Dominik
2010-11-27 2:53 ` Nick Dokos
2010-11-27 7:09 ` Manuel Hermenegildo
2010-11-27 11:22 ` Rainer Stengele
2010-11-27 11:21 ` Rainer Stengele
2010-11-27 17:00 ` Nick Dokos
2010-11-27 18:25 ` Rainer Stengele
2010-11-27 19:23 ` Nick Dokos
2010-11-27 21:11 ` Rainer Stengele
2010-11-28 0:30 ` Nick Dokos
2010-11-28 18:38 ` Rainer Stengele
2010-11-28 20:01 ` Nick Dokos
2010-11-28 20:17 ` Eric S Fraga
2010-11-28 22:11 ` Nick Dokos
2010-11-30 12:28 ` Eric S Fraga
2010-11-28 21:41 ` Rainer Stengele
2010-12-15 11:47 ` Eric S Fraga
2010-11-28 17:37 ` Eric S Fraga
2010-11-28 19:29 ` Nick Dokos
2010-11-28 19:40 ` Rainer Stengele
2010-11-28 21:32 ` Nick Dokos
2010-11-28 22:12 ` Eric S Fraga
2010-11-28 22:31 ` Nick Dokos
2010-11-29 8:53 ` Rainer Stengele
2010-11-29 10:51 ` Rainer Stengele
2010-11-29 15:56 ` Nick Dokos
2010-11-29 16:15 ` Sébastien Vauban
2010-11-30 12:30 ` Eric S Fraga
2010-12-01 14:18 ` Carsten Dominik
2010-12-01 15:11 ` moving in the agenda view is slow: solved! Rainer Stengele
2010-12-01 15:19 ` Carsten Dominik
2010-12-01 17:30 ` Eric S Fraga
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=87pqt4lzrp.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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.
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).