Re: [Nmh-workers] Future directions for nmh

2016-03-12 Thread Paul Vixie
Ken Hornstein wrote: i don't know exactly how to match mime to the simplicity of show(1), and i've been violently repulsed any time i tried to use mhshow(1), but i I can't really blame you on that one. But really, mhshow(1) is really just the old mhn, slightly rewritten. And mhn was a

Re: [Nmh-workers] Maybe time for a new release?

2016-03-12 Thread norm
>Norm wrote: > >> I want to output to stdout all the lines of that part that contain the >> string "family". What command go I feed into 'grep family"? > >Well, it depends whether you want to modify the message on disk or not. > >If you do want to modify the message permanently: > >$ mhfixmsg $

Re: [Nmh-workers] Future directions for nmh

2016-03-12 Thread norm
n...@dad.org writes: Correction: >Hear, Hear. But I assume and hope that you are talking about new commands >rather than more arguments to additional commands. I meant: Hear, Hear. But I assume and hope that you are talking about new commands rather than more arguments to existing commands.

Re: [Nmh-workers] Future directions for nmh

2016-03-12 Thread norm
Ken Hornstein writes: >But I have to ask about the idea of going from one MIME part to another; >do you really want to do that? I can only go on how I interact with >messages; almost always, I want to read the text part, and then interact >in some other way with non-text parts

Re: [Nmh-workers] Future directions for nmh

2016-03-12 Thread Paul Fox
ken wrote: > Alright, I see where you're going with this. Fair enough; that's not > how I personally work with MIME messages, but enough people have said > that they want this (and Paul even wrote something that does it!) that > clearly this UI fills a need. > > But ... let's take a step

Re: [Nmh-workers] Future directions for nmh

2016-03-12 Thread Ken Hornstein
>i don't know exactly how to match mime to the simplicity of show(1), and >i've been violently repulsed any time i tried to use mhshow(1), but i I can't really blame you on that one. But really, mhshow(1) is really just the old mhn, slightly rewritten. And mhn was a horrible hack, we all

Re: [Nmh-workers] Future directions for nmh

2016-03-12 Thread David Levine
Laura wrote: > but I would be seriously inconvenienced if mh directory mail store > went away. Enough of us would also, I expect, that this won't happen. At least at some layer that the user can see. David ___ Nmh-workers mailing list

Re: [Nmh-workers] Future directions for nmh

2016-03-12 Thread Paul Fox
paul vixie wrote: > Ken Hornstein wrote: > >> Well, it depends on the message. Sometimes I get a message with 20 photos > >> attached. I just want to be able to easily go from one to the next > >> without > >> having to type their part number. > > > > But ... what's wrong with doing