From: Harry Putnam <reader@newsguy.com>
Subject: Re: Mechaincal question Show filename of # marked
Date: 21 Dec 2000 06:28:01 -0800 [thread overview]
Message-ID: <m2bsu597da.fsf@gnus-5.8.8-cvs.now.playing> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "21 Dec 2000 11:02:40 +0100"
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> On 20 Dec 2000, Harry Putnam wrote:
>
> > Is there some quick easy way of extracting the filenames of messages
> > that are process marked?
>
> The variable gnus-newsgroup-processable contains a list of article
> numbers. The variable gnus-newsgroup-name contains the group name.
>
> With
>
> (mapcar (lambda (g)
> (expand-file-name g (gnus-group-real-name gnus-newsgroup-name
> "~/Mail/")))
> gnus-newsgroup-processable)
>
> you should be able to get a list of file names. But this only works
> for nnml and nnmh groups. This code is not tested. Does it work?
The variables do in fact hold the information I want. So theres a big
jump up... Now since I'm a no-lisp reading moron.. I'm not sure what
your code is supposed to do. Or what I should do with it.
I assumed it was intended to be evaluated...
So with the variables giving this information:
gnus-newsgroup-name's value is
"nnml:ding3" <== the ding@gnus.org list
-o-
gnus-newsgroup-processable's value is
(17 53 22 16 8 7)
Local in buffer *Summary nnml:ding3*; global value is
nil
Evaling your code gives me:
M-: (mapcar (lambda (g)
(expand-file-name g (gnus-group-real-name gnus-newsgroup-name
"~/Mail/")))
gnus-newsgroup-processable) <RET>
nil
next prev parent reply other threads:[~2000-12-21 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-21 3:06 Harry Putnam
2000-12-21 10:02 ` Kai Großjohann
2000-12-21 14:28 ` Harry Putnam [this message]
2000-12-21 15:42 ` Kai Großjohann
2000-12-21 15:55 ` Harry Putnam
2000-12-22 3:15 ` Colin Walters
2000-12-22 5:10 ` Harry Putnam
2000-12-22 6:05 ` Colin Walters
2000-12-22 8:44 ` Kai Großjohann
2000-12-22 8:40 ` Kai Großjohann
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=m2bsu597da.fsf@gnus-5.8.8-cvs.now.playing \
--to=reader@newsguy.com \
/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).