AddParam/EndParam seems to get carried away with quoting when
fed, via EXTERNAL, a URL containing a "?".

I have this line in lynx.cfg:

EXTERNAL:http:${HOME}/bin/lynx -nopause -blink -cfg=~/lib/lynx.cfg %s:TRUE

When I hit "." on this URL:

http://www.feedmag.com/feature/cx306_master.html?alert

the resulting trace is:

                Lynx Trace Log (2.8.3dev.22)

User message: Trace ON!
PARAM-ADD:${HOME}/bin/lynx -nopause -blink -cfg=~/lib/lynx.cfg 
''"'"'http://www.feedmag.com/feature/cx306_master.html?alert'"'"''
PARAM-END:${HOME}/bin/lynx -nopause -blink -cfg=~/lib/lynx.cfg 
''"'"'http://www.feedmag.com/feature/cx306_master.html?alert'"'"''
User message: ${HOME}/bin/lynx -nopause -blink -cfg=~/lib/lynx.cfg 
''"'"'http://www.feedmag.com/feature/cx306_master.html?alert'"'"''
stop_curses: done.
LYSystem(${HOME}/bin/lynx -nopause -blink -cfg=~/lib/lynx.cfg 
''"'"'http://www.feedmag.com/feature/cx306_master.html?alert'"'"'')
start_curses: done.
GridText: HText_pageDisplay at line 1 started
GridText: HText_pageDisplay finished

, the spawned lynx exits immediately, and I'm back where I
started.  URLs without "special characters" work as expected.  I
haven't tried it yet with any other characters (=, &, etc.).

In case anybody's curious, the reason for the EXTERNAL is:

LYNX_CFG in my environment points to lxrules.cfg, which contains
some lines like:

RULE:Redirect http://www.feedmag.com/feature/*_master.html?alert 
http://www.feedmag.com/feature/*lofi.html

to go directly to the relatively uncluttered, "printer-friendly"
versions of articles on frequently visited sites.  lxrules.cfg also
INCLUDE's the regular lynx.cfg for all the other settings.  When
I want to see the non-redirected page, "." starts a lynx in a
subshell, and the -cfg=... overrides LYNX-CFG and bypasses the
RULE's, until I quit that lynx and exit the subshell, ending up
back where I started.  It sounds laborious, but I think it works
pretty slick in practice.  If anybody can suggest a more direct
method, I'm interested.

-- 
Michael Warner
<[EMAIL PROTECTED]>

Reply via email to