> From: Christopher Faylor [mailto:[EMAIL PROTECTED]
>
> On Thu, Mar 13, 2003 at 04:51:24PM -0500, Christopher Faylor wrote:
> >On Fri, Mar 14, 2003 at 08:46:13AM +1300, Ross Smith wrote:
> >>> From: Christopher Faylor [mailto:[EMAIL PROTECTED]
> >>>
> >>> On Wed, Mar 12, 2003 at 11:08:27PM +0100
On Thu, Mar 13, 2003 at 04:51:24PM -0500, Christopher Faylor wrote:
>On Fri, Mar 14, 2003 at 08:46:13AM +1300, Ross Smith wrote:
>>> From: Christopher Faylor [mailto:[EMAIL PROTECTED]
>>>
>>> On Wed, Mar 12, 2003 at 11:08:27PM +0100, Anton Ertl wrote:
>>> >
>>> >If so, how should I deal with path
On Fri, Mar 14, 2003 at 08:46:13AM +1300, Ross Smith wrote:
>> From: Christopher Faylor [mailto:[EMAIL PROTECTED]
>>
>> On Wed, Mar 12, 2003 at 11:08:27PM +0100, Anton Ertl wrote:
>> >
>> >If so, how should I deal with path names where parts of the path come
>> >from ordinary windows users?
>>
>>
> From: Christopher Faylor [mailto:[EMAIL PROTECTED]
>
> On Wed, Mar 12, 2003 at 11:08:27PM +0100, Anton Ertl wrote:
> >
> >If so, how should I deal with path names where parts of the path come
> >from ordinary windows users?
>
> Either tell your Windows users to use forward slashes, tell them to
r Meinert
|=> -Original Message-
|=> From: Gareth Pearce [mailto:[EMAIL PROTECTED]
|=> Sent: Thursday, March 13, 2003 9:27 AM
|=> To: Dieter Meinert; [EMAIL PROTECTED]
|=> Subject: Re: Mixing / and \ path separators
|=>
|=>
|=> A quick search for illegal filename characters
|=>
essage-
|=> From: Christopher Faylor [mailto:[EMAIL PROTECTED]
|=> Sent: Thursday, March 13, 2003 8:53 AM
|=> To: [EMAIL PROTECTED]
|=> Subject: Re: Mixing / and \ path separators
|=> Importance: High
|=>
|=>
|=> On Thu, Mar 13, 2003 at 06:43:28PM +1100, Gareth Pea
Dieter Meinert
|=> -Original Message-
|=> From: Christopher Faylor [mailto:[EMAIL PROTECTED]
|=> Sent: Thursday, March 13, 2003 8:53 AM
|=> To: [EMAIL PROTECTED]
|=> Subject: Re: Mixing / and \ path separators
|=> Importance: High
|=>
|=
On Thu, Mar 13, 2003 at 06:43:28PM +1100, Gareth Pearce wrote:
>> Cygwin "likes" paths with backslashes in them. It now just wisely
>> assumes that such paths are windows paths. As I'm sure you know,
>> you don't use '/' to denote a UNIX path.
>
>^
>meanness detected.
Actually, more like stupidi
> Cygwin "likes" paths with backslashes in them. It now just wisely
> assumes that such paths are windows paths. As I'm sure you know,
> you don't use '/' to denote a UNIX path.
^
meanness detected.
Gareth
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:
On Wed, Mar 12, 2003 at 11:08:27PM +0100, Anton Ertl wrote:
>Cygwin 1.3.18(0.69/3/2) handles filenames like
>
>/usr/local/share/gforth/0.5.9-20030201\kernl32l.fi
>
>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
>n
On Wed, 12 Mar 2003, Anton Ertl wrote:
> 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\kernl32l.fi
> > >
> > > all right, where the "\" is meant as a path separator
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\kernl32l.fi
> >
> > all right, where the "\" is meant as a path separator. Cygwin
> > 1.3.19(0.71/3/2) and 1.3.20 reportedly do
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\kernl32l.fi
>
> 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
13 matches
Mail list logo