[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH
From: |
dickey |
Subject: |
Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH |
Date: |
Sat, 24 Apr 1999 18:04:41 -0400 (EDT) |
>
> On Sat, 24 Apr 1999 address@hidden wrote:
>
> > > I afraid we have to expect similar behaviour on VMS port - as I
> > > understand,
> > > the VMS filename always contains ':'. I see several variants (not
> > > mutually
> > > exclusive)
> >
> > perhaps simpler: require that the include filename be quoted to get
> > keywords
> > after it
> What do you mean by qouting - including the name in qoutes or escaping
> colons?
including the name in quotes.
if no quotes are given, we use the old (before your change) behavior,
which uses the remainder of the line as the pathname.
> IMO this is bad solution - it breaks backward compatibility on DOS since
> each file path contain ':' after drive letter there. So we can be smart to
^may (you don't have to have a drive letter)
> handle this without escaping colons or don't require to escape the 1st colon.
>
> I still don't know anything about VMS filenames. Can you describe them
> briefly or point which of the variants in my original letter is correct?
VMS can have more than one ':' in a pathname. Here's a few examples
filename
[dir1]filename
device:[dir1]filename
node::device:[dir1.dir2]filename
(any of the parts of a VMS pathname is optional)
>
> > > 1) On DOS - if that ':' is preceeded with letter and nothing else
> > > (perhaps
> > > spaces), we can treat such first ':' as part of the name, and expect
> > > option
> > > names to start after second ':'.
> > > 2) I don't know anything about VMS filesystem approach, so here is
> > > conditional
> > > solution:
> > > If each VMS pathname contain _exactly_ one colon, then we can expect
> > > option
> > > names after second colon, otherwise
> > > disable this functionality for VMS (since this feature is designed for
> > > ISPs
> > > that provide shell account with lynx, and IMO there are few ISPs with VMS
> > >
> > > installed, then this decision won't be painful)
> > >
> >[...]
>
> Best regards,
> -Vlad
--
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey
- Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH, (continued)
- Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH, Leonid Pauzner, 1999/04/26
- Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH, Vlad Harchev, 1999/04/26
- Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH, Leonid Pauzner, 1999/04/27
- Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH, Vlad Harchev, 1999/04/28
- Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH, Doug Kaufman, 1999/04/28
- Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH, Vlad Harchev, 1999/04/28
Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH, dickey, 1999/04/24
Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH,
dickey <=
Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH, dickey, 1999/04/25
Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH, dickey, 1999/04/26
Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH, dickey, 1999/04/26