Re: [Nmh-workers] nmh not using w3n or elinks

[norm]

Ken Hornstein <address@hidden> writes:
>>>.... so it looks like it's only using lynx right now.  As David points
>>>out, it can really only use one.  This is what you have right now:
>>>
>>>mhshow-show-text/html: charset=%{charset}; %p/usr/bin/lynx -child -dump
>>>-force-html ${charset:+--assume_charset "$charset"} %F
>>
>>When you say this is "what you have right now", do you mean that I have
>>somehow deviated from the nmh out-of-the-box defaults? I certainly
>>didn't intend to. Nor do I know how or when I did.
>
>That line above is the line that exists in the mhn.defaults you just
>sent out.  That's what I mean by "that's what you have now".  That
>line was created by the nmh build process.

Could that be because, when I configured, buile and installed nmh, I had
not yet installed w3n or elinks ?

>>>If you want to use another one, you could configure it in your own
>>>profile.  The line nmh puts in there would look like this:
>>
>>I want to use whatever is necessary for the experiment we are conducting
>>about the use of show, by me, with out-of-box-defaults. Would you send
>>me instructions for so doing, and no more. Later, if need be, I will
>>worry about customizing show.
>
>Sure.  It looks like right now, today, mhshow will use lynx for HTML
>content based on what you sent out.  So you could try that.  If you want
>to try something like w3m and you don't want to put that line I sent
>out in my previous email, then follow the other steps I sent out in
>my previous email to rebuild your mhn.defaults and reinstall.
>
>--Ken

    Norman Shapiro