Message-Id: <200502080725.j187PZZS027483@delorie.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: From: To: Cc: Subject: Re: bash: tab completion failure from (but not at) / Date: Tue, 8 Feb 2005 07:19:01 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-UoD-Spam-Score: -4.7 (----) X-UoD-Spam-Report: -------------------------------------------------- This message has been scanned by a SpamAssassin installation on the spam checking server hughtoo at the University of Dundee. Content analysis details: (-4.7 hits, 5.0 required) 0.2 NO_REAL_NAME From: does not include a real name -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] X-UoD-Scan-Signature: 5addeb9051deb8bbe06d43ff089d8fa2 Note-from-DJ: This may be spam 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 immediate and effective fix at http://www.cygwin.com/ml/cygwin/2004-05/msg00449.html but which has re-emerged in recent snapshots, at least since http://www.cygwin.com/ml/cygwin/2004-12/msg00838.html, in which Corinna records her perplexity ("weird") at this re-emergence. Things worked properly in snapshot 20041222 but fail from 20041223. Thanks. Fergus -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/