From: Shaddy Baddah <lithium-cygwin@shaddybaddah.name>
To: cygwin@cygwin.com
Subject: bad bash tab completion
Date: Fri, 10 Aug 2012 14:25:00 -0000 [thread overview]
Message-ID: <5024B4D4.6080409@shaddybaddah.name> (raw)
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
next reply other threads:[~2012-08-10 7:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 14:25 Shaddy Baddah [this message]
2012-08-10 16:54 ` Eric Blake
2013-01-14 5:21 ` stat() and tilde prefix (was bad bash tab completion) Shaddy Baddah
2013-01-14 6:17 ` Christopher Faylor
2013-01-14 12:23 ` Corinna Vinschen
2013-01-14 14:37 ` Shaddy Baddah
2013-01-14 16:13 ` Corinna Vinschen
2013-01-14 20:29 ` Stephan Mueller
2013-01-14 21:37 ` Ryan Johnson
2013-01-15 8:44 ` Corinna Vinschen
2013-01-15 12:33 ` Shaddy Baddah
2013-02-07 7:00 ` Shaddy Baddah
2013-02-07 15:32 ` Eric Blake
2013-02-07 16:10 ` Thomas Wolff
2013-02-07 16:24 ` Corinna Vinschen
2013-02-07 16:26 ` Christopher Faylor
2013-01-14 15:27 ` Christopher Faylor
2013-01-14 16:05 ` Corinna Vinschen
2013-01-14 17:00 ` Christopher Faylor
2013-01-14 22:15 ` Thomas Wolff
2013-01-15 8:56 ` Corinna Vinschen
2013-01-15 19:50 ` Andrey Repin
2013-01-15 20:03 ` Larry Hall (Cygwin)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5024B4D4.6080409@shaddybaddah.name \
--to=lithium-cygwin@shaddybaddah.name \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).