From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: SOP or other forward functions get reverse order
Date: Sun, 01 Jan 2006 15:46:37 +0900 [thread overview]
Message-ID: <b4mirt41m42.fsf@jpl.org> (raw)
In-Reply-To: <83d5jj4oiz.fsf@torus.sehlabs.com>
>>>>> In <83d5jj4oiz.fsf@torus.sehlabs.com>
>>>>> "Steven E. Harris" <seh@panix.com> wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> So, when you send a digest of articles, you'd better always specify
>> marks or a region.
> When designating a region, will the articles be ordered from top to
> bottom? That seems like the most obvious behavior, but I just want to
> make sure.
Maybe yes, though I'm not quite sure of it. In that case, the
functions `gnus-summary-work-articles' and `gnus-summary-find-next'
determine the order of articles, which reflects the order
displayed in the summary buffer.
I'm sorry for the late response.
prev parent reply other threads:[~2006-01-01 6:46 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
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 [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=b4mirt41m42.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).