Ken wrote:
[Jerrad:]
Not from the command line. It uses LANG/LC_CTYPE/LC_ALL,
and this can be overridden from the Setup>Character set menu;
which could probably set in a dummy config pointed to be -config
if one were very keen to do so, though nmh understandly is not.
The way I read the elinks documentation, it uses
LANG/LC_CTYPE/LC_ALL for display, on its output side. I
don't know how it determines the charset of its input.
As for w3m, it's installed on my machine (/usr/bin/w3m),
but the build nmh process did not pick it up.
I changed mhn.defaults.sh so that it should now.
Not sure we want to fix it for 1.6, but it looks like those things
are done via etc/mhn.defaults.sh (which uses mhn.find.sh). It
occurs to me that Autoconf might do a better job here.
mhn.defaults needs to be loaded at install time, not
configure time. I'm thinking in terms of packages/RPMs that
are created on one machine and then installed on many
others. The nmh package/RPM builder doesn't know what else
the user will install.
The alternative would be to for us, or package maintainers,
to specify dependencies on specific packages that provide
the display program(s). I don't think what we should do that.
David
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers