> "Denis A. Doroshenko" wrote:
> > the main things i would like to see in lynx:
> >
> > * SSL support
See other responses and lynx-dev archives.
> > * <TABLE> support
Some simple tables are better supported in the current code[*].
> > * more flexible way to allow/disable cookies (why if i allow cookies
> > for domain mail.yahoo.com, when i come to f17.mail.yahoo.com it
> > asks again?)
If the domain doesn't match according to the specs, then you *should*
be asked again.
But the current code[*] has various new options (and corrections)
over your old 2.8rel.2. Yous should look into it.
> > * more frexible no_proxy: option, why lynx tries to match only what
> > i entered in URL, and doesn't look for resolved addresses (if
> > i write "no_proxy:localhost" and run lynx as "lynx 127.0.0.1"
> > it will go through proxy :-(
One could regard this as a feature. I do.
> > also i would like to use wildcards
> > like "no_proxy:*.lan"; it would be cool to have something like
> > "no-proxy" command line option, to start lynx in no proxy mode
> > regardless to cfg files
Excerpt from the current code[*]'s lynx.cfg:
# The no_proxy variable can be a comma-separated list of strings defining
# no-proxy zones in the DNS domain name space. If a tail substring of the
# domain-path for a host matches one of these strings, transactions with that
# node will not be proxied.
There are no command line options for this, but you can achieve the same
effect with environment variables.
The current code[*] also has an alternative way for specifying proxies,
look into RULESFILE and cernrules.txt.
> > is there any plans to add these? both of them are implemented in w3m
> > browser, but it's very uncomfortable in other ways (it's much less
> > flexible with charset handling, it's very important to me, as browse
> > pages with three russian charsets; its URL parsing sucks; it is
> > run in much less comfortable way than lynx, although command line
> > -no-proxy option rules; etc.).
> >
> > also i have several questions about lynx:
> > * why does it looks at several <br> tags like at single one? it's said
> > that it's better to use <br><br> than <p> (which is not flexible, when
> > i don't need to give a paragraph special options), but whith lynx it
> > doesn't work
This should be controllable with COLLAPSE_BR_TAGS.
> > * why i can change "^A)ssume charset if unknown", but lynx doesn't save
> > the choosen value to .lynxrc?
Some 'O'ptions just never get saved to .lynxrc. Good or bad, you have
to live with it, for now (and probably the foreseeable future).
> > * is there way to see whole source when it contains very long lines (more
> > than number of columns on screen)
Yes, in the current code[*].
> > I use Lynx 2.8rel.2 under OpenBSD (the version that comes with OpenBSD)
[*] Your version is old. See <http://lynx.isc.org/current/> for the
current code.
Klaus
