[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH
From: |
Vlad Harchev |
Subject: |
Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH |
Date: |
Mon, 26 Apr 1999 23:11:49 +0500 (SAMST) |
On Mon, 26 Apr 1999, Doug Kaufman wrote:
> On Mon, 26 Apr 1999, Doug Kaufman wrote:
>
> > On Mon, 26 Apr 1999, Vlad Harchev wrote:
> >
> > > ...
> > > > > name is unquoted, and look for it if quoted. And how users will
> > > > > be able to quote filenames with '"' in them - the '\' is already
> > > > > used on MSDOS, so we have to invent another escape character if
> > > > > we accept quoting...
> >
> > I am a little confused by this, since I always use the forward
> > slash convention (DJGPP accepts either). I had thought that DOS
> > pathnames with backslashes required quoting in lynx.cfg (e.g.
> > c:\\lynx\\lynx.cfg). Do we really have code that accepts unquoted
> > backslashes for DOS paths?
>
> I got to check this on my DOS machine, and see that unescaped
> backslashes are accepted in DOS filenames in lynx.cfg. Is it possible
> to require forward slash in filenames for INCLUDE, so that backslash
> can be used for quoting, or is the code for DOS to accept backslashes
> too integrated to avoid here?
We have a lot of settings in lynx.cfg that accept filenames. Allowing
backslash as escape character will give precedent of supporting backslashes
(as escape characters) in other settings, and this will require a lot of work,
and will be backward incompatible (IMO).
> Doug
> __
> Doug Kaufman
> Internet: address@hidden (preferred)
> address@hidden
>
Best regards,
-Vlad
- Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH, (continued)
Re: lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH, dickey, 1999/04/26