X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=1.7 required=5.0	tests=BAYES_00,FROM_12LTRDOM,TW_YG
X-Spam-Check-By: sourceware.org
Message-ID: <5024B4D4.6080409@shaddybaddah.name>
Date: Fri, 10 Aug 2012 17:14:28 +1000
From: Shaddy Baddah <lithium-cygwin@shaddybaddah.name>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.5) Gecko/20120624 Icedove/10.0.5
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: bad bash tab completion
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Hi,

I've been having this problem with bash for about half a year now. I
can't remember the specific upgrade that caused it, but that's around
the time frame.

So the issue is with tab completion, and looks something like this:

snapshot 1:

$ cd ~/../

snapshot 2 (after tab-tab):

$ cd \~/../

snapshot 3 (after further tab-tab):

$ cd \~/../
.ssh/     tmp/      workarea/

My main problem is with snapshot 2. By my understanding, the path that
bash has modified to is no longer a valid path. snapshot 3, and further
actions from there back it up, because bash is no longer looking in the
right place.

I have tried this with bash-completions disabled, and the same thing
happens.

I do have a non-conventional setup of my home directory:

$ echo ~
/cygdrive/c/Users/sbaddah/cygwin-home

A hunch of mine is that the contents of ~/../, aka
/cygdrive/c/Users/sbaddah/, are involved. As recent Windows editions
seem to include a lot of "virtual" type folders/links that I've never
quite got my head around/


In lieu of providing a cygcheck.out, which I will do if it is absolutely
necessary. here are the details of my cygwin install:

$ uname -a
CYGWIN_NT-6.1-WOW64 AUD-R87FXYH 1.7.16(0.262/5/3) 2012-07-20 22:55 i686 
Cygwin

$ cygcheck -cd bash
Cygwin Package Information
Package              Version
bash                 4.1.10-4

Any ideas?

-- 
Regards,
Shaddy


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

