This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Mixing / and \ path separators

Igor Pechtchanski wrote:
> On Wed, 12 Mar 2003, Anton Ertl wrote:
> > Cygwin 1.3.18(0.69/3/2) handles filenames like
> >
> > /usr/local/share/gforth/0.5.9-20030201\
> >
> > all right, where the "\" is meant as a path separator.  Cygwin
> > 1.3.19(0.71/3/2) and 1.3.20 reportedly do not like such names (file
> > not found).  Is this intentional and will it stay that way?
> This is intentional.  See <>,
> especially the line that says:
> - Make handling of \foo\bar equivalent to /foo\bar.  (Christopher Faylor)
> (the above should be the other way around, but you get the idea).

Thanks (No, I don't get the idea, but I trust you:-).

> > If so, how should I deal with path names where parts of the path come
> > from ordinary windows users?
> Translate them to Unix paths using, for example, "sed 's!\\!/!g'.

Ok.  Can we leave the drive letters in place, or do we need to
translate them, too (into /cygdrive/..., right)?  I.e., is
"c:/this/that" ok?  In 1.3.18 it is.

> Does the windows port of Gforth know about POSIX paths?

Yes.  It treats both '/' and '\' as path separators, but that's easy
to change.

- anton

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]