From: "Georg C. F. Greve" <greve@fsfeurope.org>
To: ding@gnus.org
Subject: Re: Moving article and finding out where it went (URL)
Date: Wed, 18 Jul 2007 12:32:11 +0200 [thread overview]
Message-ID: <m3hco2c89g.fsf@cerebro.fsfeurope.org> (raw)
In-Reply-To: <m37ip1evh5.fsf@cerebro.fsfeurope.org> (Georg C. F. Greve's message of "Sun, 15 Jul 2007 13:51:02 +0200")
[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]
FYI.
There is a followup/related discussion to this question at
http://article.gmane.org/gmane.emacs.orgmode/2451
and in particular
http://article.gmane.org/gmane.emacs.orgmode/2457
"Moving email is trivial -- you just need to call
gnus-summary-move-article
to move things to the place you want to archive them. But that function
does not return the URL of the moved article (as one might hope).
So I see two possibilities, essentially:
a) pull it out of the function and subfunctions
b) (when moving to a backend that uses NOV databases, like nnfolder)
pull it out of the NOV file, the last moved message is the last one
on the list
Of the two, method a) seems cleaner in principle, but it requires a
fair amount of knowledge of the gnus internals -- and the change would
have to make it back into gnus, otherwise the method could break
inconveniently timed in the future.
Method b) is easier and does not require changing the main body of gnus
code, but is somewhat messy and inelegant.
So in effect I was wondering whether I missed a method c) -- and
whether anyone had already thought about either a) or b)."
Regards,
Georg
--
Georg C. F. Greve <greve@fsfeurope.org>
Free Software Foundation Europe (http://fsfeurope.org)
Join the Fellowship and protect your freedom! (http://www.fsfe.org)
What everyone should know about DRM (http://DRM.info)
[-- Attachment #2: Type: application/pgp-signature, Size: 306 bytes --]
prev parent reply other threads:[~2007-07-18 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 11:51 Georg C. F. Greve
2007-07-18 10:32 ` Georg C. F. Greve [this message]
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=m3hco2c89g.fsf@cerebro.fsfeurope.org \
--to=greve@fsfeurope.org \
--cc=ding@gnus.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).