Re: questions about the Previous-Sequence

2020-03-23 Thread Valdis Klētnieks
On Mon, 23 Mar 2020 13:16:56 +0100, Philipp said: > [2020-03-22 14:53] Ken Hornstein > > >We think currently about removing the Previous-Sequence support for > > >mmh. But because we don't use it we are not sure, if we missed some > > >aspect of it. Therefor I would like to ask some questions. >

Re: questions about the Previous-Sequence

2020-03-23 Thread Philipp
[2020-03-22 21:13] Conrad Hughes > One of the things I use it for is "unseeing" a message. Let's say I see > someone has emailed me, I'm about to go out, want to take a peek at the > message but don't want to mark it as seen — or alternatively I look at a > message, think "gosh that's gonna take

Re: questions about the Previous-Sequence

2020-03-23 Thread Philipp
[2020-03-22 14:53] Ken Hornstein > >We think currently about removing the Previous-Sequence support for > >mmh. But because we don't use it we are not sure, if we missed some > >aspect of it. Therefor I would like to ask some questions. > > I personally find the previous-sequence rather useful

Re: questions about the Previous-Sequence

2020-03-23 Thread Ralph Corderoy
Hi Conrad, > show !*; mark -sequence un -add ditto > > I bet there are magic command line switches to do this now (seems to > happen half the time I post these days!) There's show -file `mhpath .` that may give some success depending on your showproc and whether mhshow(1) is run by

Re: questions about the Previous-Sequence

2020-03-23 Thread Ralph Corderoy
Hi Ken, > I personally find the previous-sequence rather useful myself (when you > find, for example, the results of "pick" were rather larger than you > expected and didn't put it in a sequence). But that's up to you. I don't use it, but then my .mh_profile has pick: -sequence p

Re: questions about the Previous-Sequence

2020-03-22 Thread Conrad Hughes
One of the things I use it for is "unseeing" a message. Let's say I see someone has emailed me, I'm about to go out, want to take a peek at the message but don't want to mark it as seen — or alternatively I look at a message, think "gosh that's gonna take a lot of work to deal with" so want to

Re: questions about the Previous-Sequence

2020-03-22 Thread Ken Hornstein
>We think currently about removing the Previous-Sequence support for >mmh. But because we don't use it we are not sure, if we missed some >aspect of it. Therefor I would like to ask some questions. I personally find the previous-sequence rather useful myself (when you find, for example, the

Re: questions about the Previous-Sequence

2020-03-22 Thread Philipp
[2020-03-22 14:58] Ralph Corderoy > > 1. in the shell using the same messages again and spare some typing > ... > > The first completely covered with the shell history. > > If the arguments given to the last nmh command don't have a side effect > then shell history may be useful, but > > show

Re: questions about the Previous-Sequence

2020-03-22 Thread Robert Elz
Date:Sun, 22 Mar 2020 15:42:25 +0100 From:Philipp Message-ID: | The first completely covered with the shell history. Aside from what Ralph said, what shell history is that? Consider a user using dash, or some similar shell.Also consider that the commands

Re: questions about the Previous-Sequence

2020-03-22 Thread Ralph Corderoy
Hi Philipp, > 1. in the shell using the same messages again and spare some typing ... > The first completely covered with the shell history. If the arguments given to the last nmh command don't have a side effect then shell history may be useful, but show next:3 scan !$ doesn't achieve