You are not logged in.
Hello,
Some days ago I noticed that tab-completion doesn't work any more on files and directories that contain spaces. I'm pretty sure that it has. I'm using bash (3.1.17-1). I don't know when this happened, but my suspicion is that it is related to the upgrade to readline 5.2. Has anyone else experienced this? (Maybe someone can be a bit more specific than I )
Hm, here are some other perhaps interesting settings on my system:
LOCALE="en_US.ISO-8859-1"
KEYMAP="sv-latin1.map.gz"
CONSOLEFONT="lat1-16.psfu.gz"
CONSOLEMAP="8859-1"
Regards
Offline
Works fine for me.
[chris@marbles documents]$ pacman -Q | sed -ne '/bash/p;/readline/p'
bash 3.1.17-1
readline 5.2-1
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 2x160GB Maxtor DiamondMax 10, 2x320GB WD Caviar RE, Nvidia 6600GT 256MB
Laptop: Intel Pentium M, 512MB PC2700, 60GB IBM TravelStar, Nvidia 5200Go 64MB
Offline
I'm sorry, just as I saw your answer I was about to give some further info.
To be more exact my problem is that when I've tab-competed a directory containing a space, I can't hit tab again to complete file or directory names further down in the hiararchy - nothing happens.
Offline
Ahhh, that I agree with.
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 2x160GB Maxtor DiamondMax 10, 2x320GB WD Caviar RE, Nvidia 6600GT 256MB
Laptop: Intel Pentium M, 512MB PC2700, 60GB IBM TravelStar, Nvidia 5200Go 64MB
Offline
OK, good, now I don't feel so lonely any more It _has_ worked before, right?
A simple test:
$ mkdir "with space"
$ mkdir nospace
$ touch with space/hello
$ touch nospace/hi
$ ls nospace/hi <------- Here, "hi" was written just by tabbing
$ ls with space/ <------- Here tab doesn't give any result
Same thing with brackets:
$ mkdir "[brackets]"
$ touch [brackets]/hmm
$ ls [brackets]/ <------- Lots of tabbing here, no result
Also other (more or less "special") characters give this behaviour.
Offline
To be honest, I can't remember.
Just tried it on my Debian system (running Sarge), and it works fine.
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 2x160GB Maxtor DiamondMax 10, 2x320GB WD Caviar RE, Nvidia 6600GT 256MB
Laptop: Intel Pentium M, 512MB PC2700, 60GB IBM TravelStar, Nvidia 5200Go 64MB
Offline
It has, and it did break. No clues as to why, though. Pacman says bash build date is April 29, so that isn't it..
Offline
OK, I reverted to readline 5.1.4 and that works. I guess it's time for a bug report.
Offline
Bug report: http://bugs.archlinux.org/task/5915
Offline
So that's why it stopped working, I started noticing it yesterday.
PC: Antec P182B | Asus P8Z77-V PRO | Intel i5 3570k | 16GB DDR3 | GeForce 450GTS | 4TB HDD | Pioneer BDR-207D | Asus Xonar DX | Altec Lansing CS21 | Eizo EV2736W-BK | Arch Linux x86_64
HTPC: Antec NSK2480 | ASUS M3A78-EM (AMD 780G) | AMD Athlon X3 425 | 8GB DDR2 | GeForce G210 | 2TB HDD | Arch Linux x86_64
Server: Raspberry Pi (model B) | 512MB RAM | 750GB HDD | Arch Linux ARM
Offline
Bug report: http://bugs.archlinux.org/task/5915
Duplicate of bug #5912.
to live is to die
Offline
Yes, sorry. Apparently I did a lousy search
Offline
Yes, sorry. Apparently I did a lousy search
Search is not always working good. But I suggest sort bugs by date first (they are sorted by severity by default).
to live is to die
Offline
Ahh, this was driving me insane, I wish I had seen this topic earlier. I hope this gets fixed soon, it's damn annoying.
I am a gated community.
Offline
I'm struggling with the same problem for a couple of days. Once putting directory with spaces into typed path there's no more possible to complete further dirs and files in tree.
I thought that it was a kind of local configuration problem but I couldn't find any clue how to solve this situation neither in lib documentation nor on the web. Nice to know that my suspicion that there's a bug in readline is confirmed.
I'm waiting for solution (this is most annoying for me since I've got my music categorized in directories with spaces)!
It's not the best thing when they call you a "member" you know…
Offline
This issue is fixed in bash-3.2-1 from Testing.
to live is to die
Offline
Sure I'll upgrade. Thx for info!
Still I'm also interested in "why"?
It's not the best thing when they call you a "member" you know…
Offline
Still I'm also interested in "why"?
Probably due to upgrade of readline while bash was not recompiled.
to live is to die
Offline
I've recompiled bash 3.1 with the new readline, and it doesn't solve the problem.
Offline
Probably due to upgrade of readline while bash was not recompiled.
In bug report somebody mentioned that he recompiled bash against current readline without success in resolving the issue (so did slubman a moment ago). I think that's rather bash itself or bash/readline (not likely since new bash works properly) problem.
Anyway I'm stopping before I'll turn this thread into bug system I'm going to watch bug reports since now without "bugging" you (a insectorium in one phrase )
Thanks a lot for your replies and interest!
It's not the best thing when they call you a "member" you know…
Offline
Got bash from testing and pacman -U'd it manually. Works wonders and my keyboard thanks you; now he doesn't get violently blamed for lack of autocompletion.
Offline