On Tue, 17 Jul 2007, Sébastien Hinderer wrote:
Hi,
Thomas Dickey :
I don't see where the problem lies: the configure script finds the same
value as the one you want to uncomment. The compiled-in value (which
you can inspect by looking at LYNXCOMPILEOPTS:/) shows this string.
I noticed the very same problem on my system, and uncommenting the lines
SYSTEM_MAIL:/usr/mmdf/bin/submit
SYSTEM_MAIL_FLAGS:-mlruxto,cc\*
in /etc/lynx-cur/lynx.cfg
solved the problem: lynx restarted to behave in the way it always did.
None of my configs require uncommenting the value, since it's been
working as designed for a long time.
May be the pre-compiled value is overriden at some point ?
possibly. Values that are set via the configs can be traced (see the
-trace and -trace-mask options) at runtime. The compiled-in values
generally do not show up there, but (assuming that's not disabled), you
can inspect the values following the link at the bottom of the options
menu.
For example, on one of my shell accounts, following
View the file lynx.cfg.
to
See also
* compile time options
shows (just searching for "mail"):
system_mail_flags '-t -oi'
and
SYSTEM_MAIL "/usr/sbin/sendmail"
SYSTEM_MAIL_FLAGS "-t -oi"
SYSTEM_MAIL /usr/sbin/sendmail
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
