On 30 August 2000 at 10:15, John Reinhagen <[EMAIL PROTECTED]> wrote:
> just wondered if there's an architectural assumption in nmh that the order
> of a sequence is important.
>
> I notice it's not possible to advance along a sequence with commands like
> next or prev, so this suggests that order may not be important. Your
> example shows a sequence that's stored in ascending numerical order; if this
> is a strong design assumption of nmh, then I can work around that too.
More info that might help, John: MH and nmh both do sorting and
duplicate elimination when they process a string of message-number
arguments. So you can pass a list of arguments to an nmh command
with all lots of duplicates and in a weird order; the messages will
come out in numeric order, only once per message. For example:
$ scan 406 401 last:2 401
401 06/09 "Simon Butler" nmh new mail notification **rfl digest**
406 07/10 "Dan Harkless" Please post to nmh-workers if you intend to appl
409 08/18 "Dan Harkless" nmh finally listed on Yahoo!, but lamely<<Well,
410+ 08/30 John Reinhagen Questions about IMAP and sequences **rfl digest*
$ mhpath 401 401 401
/u/jpeek/Mail/m/nmh-workers/401
No matter how many times or where I list 401, it's only shown once.
This is true for all nmh commands, as far as I know.
--Jerry
P.S. This has always been a pain when I *want* to do something like
showing messages in a certain order, or with a cetain message appearing
more than once. Other than commands like these, does anyone know a way?
$ (scan 406; scan 401; scan last:2; scan 401)
$ (mhpath 401; mhpath 401; mhpath 401)
