I've got a report about Lynx's strange behavior opening localfile with
"#" on Windows.
These are the behaviors which I found, putting a file, which name is
"foo#bar", on the current directory and d:/tmp.
1. It SHOULD be opend and actually it is. (expected)
lynx -cfg=lynx.cfg -lss=lynx.lss foo#bar
2. It SHOULD be opend but actually it isn't. (unexpected)
lynx -cfg=lynx.cfg -lss=lynx.lss ./foo#bar
lynx -cfg=lynx.cfg -lss=lynx.lss d:/tmp/foo#bar
lynx -cfg=lynx.cfg -lss=lynx.lss file://localhost/d:/tmp/foo%23bar
3. It SHOULDN'T be opend and actually it isn't. (expected)
lynx -cfg=lynx.cfg -lss=lynx.lss ./foo%23bar
lynx -cfg=lynx.cfg -lss=lynx.lss d:/tmp/foo%23bar
lynx -cfg=lynx.cfg -lss=lynx.lss file://localhost/d:/tmp/foo#bar
4. It SHOULDN'T be opend but actually it is. (unexpected)
lynx -cfg=lynx.cfg -lss=lynx.lss ./foo%2523bar
lynx -cfg=lynx.cfg -lss=lynx.lss d:/tmp/foo%2523bar
lynx -cfg=lynx.cfg -lss=lynx.lss file://localhost/d:/tmp/foo%2523bar
I've tested 2.8.6rel.1 for Windows got from this URL.
http://pervalidus.50webs.org/cygwin/lynx/