Path: utzoo!attcan!uunet!seismo!sundc!pitstop!male!sun-barr!apple!oliveb!amdahl!pacbell!pbhyf!rob
From: rob@PacBell.COM (Rob Bernardo)
Newsgroups: comp.mail.elm
Subject: Re: Behavior of ' ' considered inconsistant
Message-ID: <5275@pbhyf.PacBell.COM>
Date: 12 May 89 14:36:46 GMT
References: <1415@lokkur.UUCP> <5222@pbhyf.PacBell.COM> <1114@itivax.iti.org> <5234@pbhyf.PacBell.COM> <1129@itivax.iti.org> <5257@pbhyf.PacBell.COM> <1145@itivax.iti.org>
Reply-To: rob@PacBell.COM (Rob Bernardo)
Organization: Pacific * Bell, San Ramon, CA
Lines: 28

In article <1145@itivax.iti.org> scs@vax3.iti.org (Steve Simmons) writes:
+I want the meaning of *next* [in pager mode] to match what one has 
+selected for the sorting option.  To wit:
+  if ( display order != reversed )
+    next = downward = increasing message numbers in column #2
+  else
+    next = upward = decreasing message numbers in column #2

But when you're on the index screen, next *always* means downward
(increasing message numbers), regardless of whether the sort criterion
is a reversed type or not, because the index screen listing is *already*
sorted.

So what you're wanting is for "reverse" to have two separate meanings.
For sorting on the index screen, it would mean a reverse order from
it's unreversed counterpart. For pager mode it would mean the reverse
of whatever the index screen is. Why  have one option govern two
actions in disparate ways?

The way it is now: the sort criterion is used to sequence the messages,
whether it be a reverse criterion or not. The sort sequence is used
on the index screen and next means the same thing (follows the same
order whether you are on the index  screen or in pager mode).
-- 
Rob Bernardo, Pacific Bell UNIX/C Reusable Code Library
Email:     ...![backbone]!pacbell!pbhyf!rob   OR  rob@pbhyf.PacBell.COM
Office:    (415) 823-2417  Room 4E850O San Ramon Valley Administrative Center
Residence: (415) 827-4301  R Bar JB, Concord, California