> In the screenshot above, I noticed that you use mhshow. mhshow
> expects a message number, not a file name. Did you explicitly
> instruct nmh to use mhshow as your lproc?
Nope, I've got "show" as my lproc. It's "show" that's invoking
"mhshow". That's the way it's been for months (years?) now.
I guess it's possible that something in my environment could be causing
the problem. But "What now? list" used to work on MIME messages under
MH -- and, I'm almost sure, under nmh-0.26 (or was it 0.24?), the
version that came RPM'ed with Red Hat Linux 5.1. Here are some
possibly-useful entries from my MH profile:
lproc: show
#: Keep mhn from using external pager for message header:
mhn: -nomoreproc
moreproc: less
prompter-next: vi
prompter.nopre-next: vi
showproc: mhl
vi-next: spell
#: This is just a symbolic link to "prompter" with a new name:
prompter.nopre: -noprepend -rapid
prompter.nopre-next: vi
prompter.pre: -prepend -rapid
prompter.pre-next: vi
When I use "show" from the command line, I haven't noticed any "bad
message list" complaints. "whatnow" should be invoking "show", then
"show" should see the MIME content and invoke "mhshow". So my guess
is that the problem is in the way "show" invokes "mhshow".
The only mhshow- profile entries I have are mhshow-show-<type> and
mhshow-charset-<charset>. I don't think any of them would cause this;
they're all for types that aren't in the message. (If they *are*
causing the problem, I'd wish for a more-accurate error message!)
Sorry if I'm reporting a bug that turns out not to be a bug. Maybe I
should just keep quiet when I'm not sure of the cause of a problem.
But I know that I'll never get time to really dig in.
Jerry
--
Jerry Peek, [EMAIL PROTECTED], http://www.jpeek.com/~jpeek/
