[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] Future directions for nmh

From: Paul Vixie
Subject: Re: [Nmh-workers] Future directions for nmh
Date: Fri, 11 Mar 2016 23:42:25 -0800
User-agent: Postbox 4.0.8 (Windows/20151105)

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 something like:

mhstore -type image

Then you can deal with each of those photos as a seperate file.

ui wise, i don't want files. i want to act on the attachments (view them, in this case) and then leave them stored as attachments (without having to delete any temporary files.)

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 think what i want would look a bit like whatnow(1) is to send(1). (for many years i used "send -wa" because my sendmail.cf was a hack, then i used "push" when i stopped being fascinated by SMTP traces.)

the command set i'd suggest for whatnowmime(1) would include things like:

ls | dir
        shows the full message structure (like in ftp)
cd x.y.z
        go to part x subpart y subsubpart z
        go to next attachment at same level (like in gdb)
        go to next attachment at or below the current one (like gdb)
        opposite of next
        opposite of step
        go up one level
        launch an external viewer suitable for this mimetype
        do the best you can in inline ascii for this mimetype
save [-r] [x.y.z]
save the current part (default) or part x subpart y subsubpart z, maybe recursively (-r)
        exit from mhshow(1)

P Vixie

reply via email to

[Prev in Thread] Current Thread [Next in Thread]