From: Steve Harris <sharris@primus.com>
Subject: gnus-uu-digest-mail-forward (S-O-m) nit
Date: 24 Feb 2000 08:35:03 -0800 [thread overview]
Message-ID: <svk8juwoco.fsf@hodge.primus.com> (raw)
[ I submitted this to gnu.emacs.gnus two days ago, but got no
reply. I'm not sure if my news server propagated it or not. ]
I've noticed some counter-intuitive behavior with
'gnus-uu-digest-mail-forward' (S-O-m from the Summary buffer): it
collects the articles in reverse order. That is, whatever ordering
it's using, it turns out to be the reverse of the order that the
messages originally appeared in in the Summary buffer. I don't have
any customized sorting-related settings. When I send these digests off
to a friend, I have to warn the recipient that the messages should be
read in reverse order!
Has anyone else noticed this behavior? Are there some variables I can
use to control it and force the order into something more intuitive
(such as "threaded, with oldest message first")?
--
Steven E. Harris
Primus Knowledge Solutions, Inc.
http://www.primus.com
next reply other threads:[~2000-02-24 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-24 16:35 Steve Harris [this message]
2000-02-24 16:53 ` Kai Großjohann
2000-02-24 17:33 ` Steve Harris
2000-02-24 19:32 ` Kai Großjohann
2000-02-24 21:40 ` Steve Harris
2000-02-24 22:41 ` Kai Großjohann
2000-02-24 23:23 ` Steve Harris
2000-02-25 10:45 ` 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=svk8juwoco.fsf@hodge.primus.com \
--to=sharris@primus.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).