From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: More fun with nnweb
Date: Tue, 21 Aug 2001 23:51:50 +0200 [thread overview]
Message-ID: <m3lmkdaxop.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <y68k7zy7shv.fsf@pickled-herring.mit.edu>
"David Z. Maze" <dmaze@MIT.EDU> writes:
> The bug number is unique, and I should correctly parse it out of the
> initial list-of-bugs page. This seems suggest that I would want to
> use it instead of (cdr active) as the number parameter to
> make-full-mail-header, yes?
Yup.
> Is there better documentation than C-h f for this function and how
> it's relevant to things?
Nope. There's not much documentation for nnweb.
> (It looks like the way I do things now is to parse out the URL and bug
> name from the list-of-bugs page, and then, if the URL isn't already in
> nnweb-hashtb, I do
> (push
> (list
> (incf (cdr active))
> (make-full-mail-header
> (cdr active) subject from nil nil nil 0 0 url))
> map)
> This looks like it should guarantee that each "article" has a unique
> number, but if the same thing is encountered more than once with
> different URLs, it winds up in the list multiple times.)
Yes -- you could index the table based on the bug number instead of
the URL, I think. (It's been a while since I worked with nnweb --
ShengHuo probably has more recent experiences with the internals...)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2001-08-21 21:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 17:50 David Z. Maze
2001-05-31 8:45 ` Andreas Fuchs
2001-05-31 9:45 ` Roland Mas
2001-05-31 10:00 ` Kai Großjohann
2001-05-31 10:39 ` Andreas Fuchs
2001-06-04 17:59 ` Toby Speight
2001-06-04 20:41 ` Kai Großjohann
2001-08-19 20:58 ` Lars Magne Ingebrigtsen
2001-08-20 13:47 ` David Z. Maze
2001-08-21 21:51 ` Lars Magne Ingebrigtsen [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=m3lmkdaxop.fsf@quimbies.gnus.org \
--to=larsi@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).