On Feb 8 19:58, Ronald Landheer-Cieslak wrote:
> Corinna Vinschen wrote:
> >On Feb 8 07:19, [EMAIL PROTECTED] wrote:
> >>Recent remarks ("I have an idea about how to fix the race but it would
> >>introduce a destabilizing change that I'd rather not chance before 1.5.13
> >>is
> >>released") sugg
Corinna Vinschen wrote:
On Feb 8 07:19, [EMAIL PROTECTED] wrote:
Recent remarks ("I have an idea about how to fix the race but it would
introduce a destabilizing change that I'd rather not chance before 1.5.13 is
released") suggest that an updated cygwin1.dll might be imminent.
Please could I ment
On Feb 8 07:19, [EMAIL PROTECTED] wrote:
> Recent remarks ("I have an idea about how to fix the race but it would
> introduce a destabilizing change that I'd rather not chance before 1.5.13 is
> released") suggest that an updated cygwin1.dll might be imminent.
> Please could I mention a minor but
Recent remarks ("I have an idea about how to fix the race but it would
introduce a destabilizing change that I'd rather not chance before 1.5.13 is
released") suggest that an updated cygwin1.dll might be imminent.
Please could I mention a minor but annoying glitch described along with
Corinna's imm
On Wed, May 12, 2004 at 05:43:32PM +0200, Corinna Vinschen wrote:
> On May 12 16:17, Dave Korn wrote:
> > I reckon you could quote
> > http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap04.html#tag_0
> > 4_11
> > to support the claim that what bash is doing is actually an invalid
> >
On May 12 16:17, Dave Korn wrote:
> I reckon you could quote
> http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap04.html#tag_0
> 4_11
> to support the claim that what bash is doing is actually an invalid
> transformation and should be considered a bug. That page says
>
> "A pathna
> -Original Message-
> From: cygwin-owner On Behalf Of Corinna Vinschen
> Sent: 12 May 2004 15:09
> In bash, the path "/" is accidentally converted to "//"
> before it tries
> to call opendir() on it. On any other POSIX system, that
> doesn't matter
> since "//" has no special meaning.
On May 11 07:25, [EMAIL PROTECTED] wrote:
> Just lately (all recent snapshots including 20040510) I'm noticing a failure
> with tab completion for pathnames beginning /. Thus, I would expect, and in
> the past have achieved
>
> ls /ho
> ls /home/
> or
> md5sum /usloc
> md5
* <[EMAIL PROTECTED]> (2004-05-11 08:25 +0100)
> Just lately (all recent snapshots including 20040510) I'm noticing a failure
> with tab completion for pathnames beginning /. Thus, I would expect, and in
> the past have achieved
>
> ls /ho
> ls /home/
> or
> md5sum /usloc
>
>> Interesting.
>> No problems with tcsh or zsh.
>> Just bash misbehaves.
Corinna,
Couldn't work out whether you were enquiring further into my own experience
or (as I hope and suspect) reporting yours. But yes, I get no problems with
tcsh or zsh, just as reported with bash (and, if it's worth re
On May 11 07:25, [EMAIL PROTECTED] wrote:
>
> Just lately (all recent snapshots including 20040510) I'm noticing a failure
> with tab completion for pathnames beginning /. Thus, I would expect, and in
> the past have achieved
>
> ls /ho
> ls /home/
> or
> md5sum /usloc
>
11 matches
Mail list logo
