Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<3C0F9B75.2040401@ece.gatech.edu>
Date:	Thu, 06 Dec 2001 11:23:17 -0500
From:	Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent:	Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010914
X-Accept-Language:	en-us
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: cygwin 1.3.6-3 and xemacs
References:	<Pine DOT WNT DOT 4 DOT 33 DOT 0112060937500 DOT 1404-100000 AT MSD-PC3> <20011206154936 DOT GA22573 AT redhat DOT com> <20011206155622 DOT GB22573 AT redhat DOT com>
X-Virus-Scanned:	by amavisd-milter (http://amavis.org/)

Christopher Faylor wrote:

>>>There has also been some confusion in the cygwin mailing list with another
>>>problem to do with file completion in bash: see
>>>http://sources.redhat.com/ml/cygwin/2001-12/msg00175.html . Fixing the
>>>shell file completion problem has NOT fixed the xemacs problem (although
>>>Christopher Faylor's thinking that it it might was not unreasonable).
>>>
>>I don't think I mentioned that I thought it would fix xemacs.


No, somebody on the xemcs list said "cygwin-xxxx fixes this other 
problem in bash related to cygdrive.  MAYBE it also fixes our xemacs 
problem which is related to cygdrive.  Can somebody check?"

And somebody DID check -- and reported "Nope, doesn't fix it"

End of story.

>>
>>Someone should actually *debug the problem*.
>>
> 
> Ah.  Nevermind.  I thought you were referring to my 1.3.6-4 announcement.
> The shell file completion fix was in 1.3.6-4.
> 
> You see, someone gave me enough information to actually duplicate the
> problem myself.  Sadly, I have no interest whatsoever in Xemacs, so
> providing instructions on how to duplicate a problem in Xemacs is not
> going to help me much since I don't have Xemacs installed.


I think that debugging is ongoing right now.  (But cygwin IS a moving 
target; you can't blame folks for *hoping* that the fix for problem A 
will also nail problem B...and delaying their debug efforts until after 
they get the new kernel with the A-fix.


--Chuck






--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -