From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: SOP or other forward functions get reverse order
Date: Fri, 23 Dec 2005 00:15:03 +0900 [thread overview]
Message-ID: <b4mlkyd5fk8.fsf@jpl.org> (raw)
In-Reply-To: <87ek4683ca.fsf@vera.springies.com>
>>>>> In <87ek4683ca.fsf@vera.springies.com>
>>>>> Alan Shutko <ats@acm.org> wrote:
> but here's the fix I've been using.
> --- lisp/gnus-uu.el 25 Sep 2005 21:27:49 -0000 7.20
> +++ lisp/gnus-uu.el 21 Dec 2005 22:57:34 -0000
> @@ -1127,7 +1127,7 @@
> (setq n (1- n))))
> (nreverse articles)))
> (gnus-newsgroup-processable
> - (reverse gnus-newsgroup-processable))
> + gnus-newsgroup-processable)
> (t
> (gnus-uu-find-articles-matching)))))
It will probably be a wrong approach. All the clauses of that
`cond' form seem to have to return a reversed list of article
numbers.
next prev parent reply other threads:[~2005-12-22 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 11:43 reader
2005-12-21 16:00 ` Steven E. Harris
2005-12-21 22:58 ` Alan Shutko
2005-12-22 15:15 ` Katsumi Yamaoka [this message]
2005-12-22 7:26 ` Katsumi Yamaoka
2005-12-22 7:50 ` Katsumi Yamaoka
2005-12-22 9:35 ` Katsumi Yamaoka
2005-12-23 23:10 ` reader
2005-12-26 20:00 ` Steven E. Harris
2006-01-01 6:46 ` Katsumi Yamaoka
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=b4mlkyd5fk8.fsf@jpl.org \
--to=yamaoka@jpl.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).