Re: Problem with text/html parts?
- From: Joel Reicher <joel@xxxxxxxxxxxxxxxx>
- Date: Sun, 18 Nov 2007 07:19:32 GMT
Aaron W. Hsu <arcfide@net> writes:
Ack! My, how terrible. The one time I don't verify what I post and this is
how NN repays me. Actually, no, I wrote quite a bit, which would answer the
questions you posed below, I believe. :-P I'll try to recount what is
going on.
No harm done. :)
Without a custom MH Profile, I noticed that running the 'show' command on
some messages didn't seem to display what I expected, while others would
pop up a nice textual item. Doing some reading about how to make show use
the programs I wanted, led me to start playing with my MH Profile. I added
the following entry, when I discovered that HTML mail was the one that was
failing:
mhshow-show-text/plain: %pless '%F'
I'm going to guess that you put this entry in because you were getting
xterms popping up for the display of text/plain parts, depending on
the charset. The Right Way (IMHO) to address this is with the
MM_CHARSET environment variable. From the mhshow man page:
Showing Alternate Character Sets
Because a content of type text might be in a non-ASCII character set,
when mhshow encounters a "charset" parameter for this content, it
checks if your terminal can display this character set natively. mhn
checks this by examining the the environment variable $MM_CHARSET. If
the value of this environment variable is equal to the value of the
charset parameter, then mhshow assumes it can display this content
without any additional setup. If this environment variable is not set,
mhshow will assume a value of "US-ASCII". If the character set cannot
be displayed natively, then mhshow will look for an entry of the form:
mhshow-charset-<charset>
which should contain a command creating an environment to render the
character set. This command string should containing a single "%s",
which will be filled-in with the command to display the content.
The reason why an environment variable is probably the right solution
for this is that its setting needs to be terminal-dependent, which may
change from login to login. In most of my environments I have it set
to "iso-8859-1".
Of course, my guess could be way off. :) If all you wanted was to
change your pager (which might have a builtin default of "more") then
you should use
moreproc: less
in your MH profile.
mhshow-show-text/html: %plynx '%F'
Okay, so that is more than one entry. But, at any rate, I expected it to
work, since opening text/plain parts works just fine with the above
entries.
I am using nmh-1.0.4 on OpenBSD.
You might want to consider upgrading to at least 1.2, and perhaps even
to CVS.
When it still did not work, I checked the error message that I was getting
which is something like:
/tmp//lynx-OdZTr11926/: No such directory
exit 1
Not exactly the greatest thing to see. :-) Do you know what could be going
on?
I'm reasonably certain this is a lynx error. I can't imagine mhshow
using the string "lynx" in any temporary pathnames, but I could be
wrong.
Could you try
mhshow-show-text/html: %pless '%F'
in your MH profile? If it works, you know immediately that lynx is the
problem.
The only other thing I can think of is that you might have set up a
content cache somewhere; have you been experimenting with caching?
Cheers,
- Joel
.
- Follow-Ups:
- Re: Problem with text/html parts?
- From: Aaron W . Hsu
- Re: Problem with text/html parts?
- References:
- Problem with text/html parts?
- From: Aaron W . Hsu
- Re: Problem with text/html parts?
- From: Joel Reicher
- Re: Problem with text/html parts?
- From: Aaron W . Hsu
- Problem with text/html parts?
- Prev by Date: Re: Problem with text/html parts?
- Next by Date: Re: Problem with text/html parts?
- Previous by thread: Re: Problem with text/html parts?
- Next by thread: Re: Problem with text/html parts?
- Index(es):
Relevant Pages
|