Re: lynx-dev -noexec

[Thomas Dickey]

On Tue, 16 Sep 2003, Pat Walsh wrote:

> * I burbled:
> > With LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE set TRUE in ~/.lynx.cfg,
> > starting lynx with -noexec results in
> >     Execution links (!)    : [FOR LOCAL FILES ONLY]
> > in the Options menu.
> >
> > With LOCAL_EXECUTION_LINKS_ALWAYS_ON, the -noexec command line option
> > results in [ALWAYS OFF] in the options menu, which is what one would
> > expect with both.
>
> ack! overlooked -locexec, the below is as it should be. Beg pardon!
>
> > Also, starting lynx with -exec (with both LOCAL_EXECUTION_LINKS_* set
> > FALSE in ~/.lynx.cfg), results in Execution links [ALWAYS ON].
>
> Am I correct regarding -noexec? that all execution links should be
> disallowed regardless of lynx.cfg settings?

It depends on how it's compiled: the "-exec" option (see LYMain.c,
exec_fun function) will either set local_exec or
local_exec_on_local_files.  Comparing with LYOptions.c, it appears
that the "ALWAYS ON" that you're seeing is for the former (local_exec)
flag.  Using the "-noexec" flag resets local_exec, so that sounds like
the answer is "yes".

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden