From: Alan Shutko <ats@acm.org>
Subject: Re: SOP or other forward functions get reverse order
Date: Wed, 21 Dec 2005 16:58:29 -0600 [thread overview]
Message-ID: <87ek4683ca.fsf@vera.springies.com> (raw)
In-Reply-To: <q947j9ysaml.fsf@chlorine.gnostech.com> (Steven E. Harris's message of "Wed, 21 Dec 2005 08:00:53 -0800")
[-- Attachment #1: Type: text/plain, Size: 464 bytes --]
"Steven E. Harris" <seh@panix.com> writes:
> Recently I tried forwarding a set of messages, and had to redo it five
> or six times because the order seemed backward, despite my having
> process-marked the messages in the desired order.
Yes, it's broken. I don't know why, cvs annotate isn't working on
that file for me, but here's the fix I've been using.
--
Alan Shutko <ats@acm.org> - I am the rocks.
Balance the budget. Declare politicians a game species!
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: gnus-uu.diff --]
[-- Type: text/x-patch, Size: 532 bytes --]
Index: lisp/gnus-uu.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus-uu.el,v
retrieving revision 7.20
diff -u -r7.20 gnus-uu.el
--- 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)))))
next prev parent reply other threads:[~2005-12-21 22:58 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 [this message]
2005-12-22 15:15 ` Katsumi Yamaoka
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=87ek4683ca.fsf@vera.springies.com \
--to=ats@acm.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).