Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH

[Leonid Pauzner]

26-Apr-99 23:18 Vlad Harchev wrote:
> On Mon, 26 Apr 1999, Leonid Pauzner wrote:

>> 25-Apr-99 06:54 Klaus Weide wrote:
>>
>> > Why not use just ' ' space?   Apart from disallowing filenames with
>> > spaces, it looks non-intuitive, as if several files were included.
>>
>> > Actually, in *this* case (not generally), I'm in favor of adding some
>> > syntactic sugar.  As in
>>
>> >   include:~/.lynx/rc for COLOR KEYMAP VIEWER SUFFIX
>>
>> I read all this thread and think Klaus' idea with space
>> and a reserved word "for" looks best.
>> There is no problem to explain this syntax in lynx.cfg
>> so nobody will be confused, and literal " for " in filenames
>> seems a very rare case (so we get an extra recovery).
>>
>> (As for my original DOS problem I set HOME variable
>> and include:~/lynx.cfg   without full path so it was expanded
>> by read_cfg() so I work around this particular case).

>  OK, scanning for specific substring (be it ' for ' or ' :') as separator is
> much simpler, than implementing quoting/escaping mechanism for a particular
> setting. Here are my wishes:
>  on unix, accept  both ':' and ' for ' as separators, and accept ' for ' only
> as separator on other OSes. Unix users, that will be confused by such "sweet"
> syntax, as ' for ', can use ':' as separator, while people on other OSes have
> to use ' for ' unconditionally.

>  Let's think more..

Be sure LYNXCFG:/ page show it properly
(it was a nice thing that notrecognized options was ommited
in this rendered output so we could track errors/typos immediately).

>>[...]
27-Apr-99 07:38 Vlad Harchev wrote:
> On Tue, 27 Apr 1999, Leonid Pauzner wrote:

>> 26-Apr-99 18:51 Vlad Harchev wrote:
>> > On Mon, 26 Apr 1999, Klaus Weide wrote:
>>
>> >> Btw. what would
>> >>
>> >>    include:c:\lynx\mylynx.cfg :
>> >>
>> >> mean? (a) everything disallowed (b) or everything allowed?
>>
>> >  (b) - Everything allowed for current file will be allowed in the included
>> > file. The same for plain
>> >  include:c:\lynx\mylynx.cfg
>>
>> And what would for these two
>>
>> include:lynx.cfg : UNKNOWN_OPTION
>> include:lynx.cfg : UNKNOWN_OPTION HELPFILE
>>
>> IMO (a) for first and HELPFILE for second.
>>

>  Yes.

>  Best regards,
>   -Vlad




>  Best regards,
>   -Vlad