https://bugzilla.novell.com/show_bug.cgi?id=725657
https://bugzilla.novell.com/show_bug.cgi?id=725657#c39
--- Comment #39 from Ashwin G 2012-10-04 16:25:45 UTC ---
Thanks Werner for the explanation. I understand it more of an upstream change
in the behavior of the bash package which is causing all these features which
have been working for couple of years to break.
Using your suggestion for ls tab-completion, it works only if there is no '/'
at the end.
For example, I have an age-old Centos machine (Centos 4 I guess) which has no
bash-completion package and it does the simple tab expansion of variables
ending with a / at the end of the variable (which is quite the natural behavior
you'd expect).
ls $PWD/<TAB>
ls $PWD/newdir<TAB> (Expands to absolute path)
Also
ls $PWD<TAB> (Just adds a space without expansion - again a naturally expected
behavior)
And I'm surprised this has just stopped working.
In fact I tried the bash-4.2-1.8.1.x86_64.rpm from openSUSE 12.1 - and it
exhibits a similar behavior as openSUSE 12.2 (I've uninstalled bash-completion
- so it is the plain bash package I'm using).
Then I switched to 11.4's bash-4.1-20.25.1.x86_64.rpm and there the feature
works without any problems. Then I installed the latest bash-completion to go
with this, and so far I've not found any problems.
I understand I can switch to tcsh or any other powerful shell like zsh - but
many of the Makefiles break in shells other than bash (even it's very close
subset cousin dash for instance).
I've written few minor additions to bash-completion in the past, but I dont
remember much of it. I guess I should go ahead and find out how to get it
working with the latest bash.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.