lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: David Combs
Subject: Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH
Date: Sun, 25 Apr 1999 18:59:27 -0700

On Tue, Apr 20, 1999 at 10:49:26PM +0500, Vlad Harchev wrote:
> On Sun, 25 Apr 1999 address@hidden wrote:
> 
> > >  Probably that character should be '*'? What lynx developers think about 
> > > it 
> > > (suggestions of characters are welcome) 
> > >  
> > >  Another idea - seems that ':' is unusual character in unix filenames - 
> > > so we 
> > 
> > not really - I use it (I do run into the problem of putting it in filenames
> > that I would try to inspect with lynx from the command-line ;-).
> 
>   Don't you use newlines in filenames? :) In this case the code in LYReadCFG.c
>  will definitely fail...
>  
>   And I think you use '*' less frequently than ':' in filenames.
> 
>   IMO we can restrict outself from using such chars in filenames of lynx
> configuration files (at least).  
>  
> > > can support this feature on unix as it is (without changing extra logic 
> > > like 
> > > quoting, escaping, etc - just ifdef'ing), and disable it on DOS,VMS, 
> > > MacOS - I 
> > > don't think there are a lot of ISP that run these OSes. 
> > >  Or we can provide this feature on these OSes, but delimiter will be 
> > > different 
> > > from ':' for them - may be '*' on these OSes and still ':' on unix? 
> > >  
> > >  So any opinions? 
> > >  
> >[...] 
> 
>  Best regards,
>   -Vlad
> 

I myself save the emacs "*Buffer list*" as *buffer-list*-26apr99.

I wonder how many others do too?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]