* Moving article and finding out where it went (URL)
@ 2007-07-15 11:51 Georg C. F. Greve
2007-07-18 10:32 ` Georg C. F. Greve
0 siblings, 1 reply; 2+ messages in thread
From: Georg C. F. Greve @ 2007-07-15 11:51 UTC (permalink / raw)
To: ding
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
Hi all,
I'm moving around mail frequently for various purposes and often find
myself wanting to know where it went (the URL, as in folder and number).
gnus-summary-move-article does not seem to support telling you where it
put something. Is there a "right" way to do this?
All help appreciated,
Best 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 --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Moving article and finding out where it went (URL)
2007-07-15 11:51 Moving article and finding out where it went (URL) Georg C. F. Greve
@ 2007-07-18 10:32 ` Georg C. F. Greve
0 siblings, 0 replies; 2+ messages in thread
From: Georg C. F. Greve @ 2007-07-18 10:32 UTC (permalink / raw)
To: ding
[-- 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 --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-07-18 10:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-07-15 11:51 Moving article and finding out where it went (URL) Georg C. F. Greve
2007-07-18 10:32 ` Georg C. F. Greve
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).