Re: [Nmh-workers] mhshow -file /tmp (!)

[Ken Hornstein]

>it's somewhat shocking how far the code gets when handed this invocation:
>    mhshow -file /tmp
>
>short answer:  way into the depths of show_content_aux(), where
>it finally hits "internal error (3)".  this leaves tempfiles unremoved,
>and, in my case, the tty is no longer in fully-cooked mode, and needs
>to be reset.

Hm.  I get:

mhshow: error reading from /tmp: Is a directory
        (content text/plain in message /tmp)

And everything seems ok.  A quick system call trace reveals that the
error is coming back from read().  I suspect there are a lot of things
that are falling back to a "mangled" message being a single text/plain
part.  Can you just open directory files without any special magic on
your system?  It would be interesting to see the logic flow.

Personally, I'm a little reluctant to require that all -file arguments
are vanilla files; I could see where it being a named pipe, for example,
might be useful.

--Ken