Re: Reading messages in a sequnce

2020-07-11 Thread aalinovi
Just a quick thank you to all who took time to respond to my original question. I've looked at mairix but feel it's a bit too involved for my needs. Mr Fox's solution works so that is what I'll go with. Arthur aalin...@riseup.net writes: >If I have non consecutive messages in a given sequence,

Re: Reading messages in a sequnce

2020-07-11 Thread Ralph Corderoy
Hi aalinovi, Paul wrote: > It's one of mh's hidden gems. Use "picked:next", "picked:first", > "picked:last", "picked:prev". I have wrapper commands that do all of > those. "picked:3" and "picked:-2" also work. > > It's in mh-sequences(1). And lots of fine detail is in

Re: Reading messages in a sequnce

2020-07-11 Thread Geoff Raye
pick -seq foo -from o...@the.cat show foo:first show foo:next show foo:next show foo:last [aalin...@riseup.net] > If I have non consecutive messages in a given sequence, is there any way > to read them consecutively? > > For example, sequence picked with messages 94 95 114 126 155. > show 94

Re: Reading messages in a sequnce

2020-07-10 Thread Paul Fox
aalin...@riseup.net wrote: > If I have non consecutive messages in a given sequence, is there any way > to read them consecutively? > > For example, sequence picked with messages 94 95 114 126 155. > show 94 shows message 94, next shows message 95. But then next shows > message 96, not

Re: Reading messages in a sequnce

2020-07-10 Thread Conrad Hughes
> If I have non consecutive messages in a given sequence, is there any way > to read them consecutively? Not quite what you're after, but if you've got the search indexer mairix installed (I highly recommend it), it creates search results in their own temporary folder, so prev and next work

Reading messages in a sequnce

2020-07-10 Thread aalinovi
If I have non consecutive messages in a given sequence, is there any way to read them consecutively? For example, sequence picked with messages 94 95 114 126 155. show 94 shows message 94, next shows message 95. But then next shows message 96, not message 114 (which makes sense since 96 is the