From: "Leonid Pauzner" <[EMAIL PROTECTED]>
> lynxcfg:/ output is the true list of cfg options visible by lynx.
> There is no difference in exact order of loaded nested cfg files, only
> the order of declarations: if lynxcfg:/ page shows several declarations
> of STARTFILE (for example) - only the last one will have an effect.
So the order _is_ important - one wants to have their customizations to
occur AFTER the defaults are specified.
> > #<begin /projects/intranet/lib/lynx/lynx.cfg.cas>
> > #<end of /projects/intranet/lib/lynx/lynx.cfg.cas>
>
> It seems that /projects/intranet/lib/lynx/lynx.cfg.cas
> file doesn't exist and could not be loaded.
$ ls -l /projects/intranet/lib/lynx/lynx.cfg.cas
-rw-r--r-- 1 lwv26 intranet 3062 May 6 05:41
/projects/intranet/lib/lynx/lynx.cfg.cas
Interestingly enough if I move the
> INCLUDE:~/.lynx.cfg
into /projects/intranet/lib/lynx/lynx.cfg, lynx reads it just fine.
So apparently I can't nest the INCLUDE's. The weird thing is that
I am pretty sure I used to be able to...
--
Larry W. Virden <mailto:[EMAIL PROTECTED]>
<URL: http://www.purl.org/NET/lvirden/>
Unless explicitly stated to the contrary, nothing in this posting should
be construed as representing my employer's opinions.
-><-
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
