https://bugzilla.novell.com/show_bug.cgi?id=752422 https://bugzilla.novell.com/show_bug.cgi?id=752422#c1 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #1 from Dr. Werner Fink 2012-03-15 11:27:50 UTC --- I know but this is how the complete works you're using the programmable complete with the +plusdirs option. If you do not like this then please use complete -r to be without any programmable complete. Please if you're knowing a solution which works for all cases then please reopen. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=752422 https://bugzilla.novell.com/show_bug.cgi?id=752422#c3 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Minor --- Comment #3 from Dr. Werner Fink 2012-03-15 13:21:50 UTC --- Then this bug has to wait as I'm very busy with SLES and have no time to handle such issues. complete -r gives you the default behaviour of the bash. You may use an other shell instead. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=752422 https://bugzilla.novell.com/show_bug.cgi?id=752422#c5 --- Comment #5 from Dr. Werner Fink 2012-03-16 08:24:46 UTC --- That is clear because bash from 12.1 does not include the patch for bug #725657. With this patch the new shell option direxpand is active .. you may try shopt -u direxpand to disable directory name expansion but then you may see the new upstream behaviour reported in bug #725657. Btw: Who is expecting what? Why does upstream change the behaviour? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=752422 https://bugzilla.novell.com/show_bug.cgi?id=752422#c7 --- Comment #7 from Jiri Slaby 2012-03-16 09:14:11 UTC --- (In reply to comment #5)

That is clear because bash from 12.1 does not include the patch for bug #725657. With this patch the new shell option direxpand is active ... you may try

shopt -u direxpand

to disable directory name expansion

Yes, that did the trick. But what side-effects this has?

but then you may see the new upstream behaviour reported in bug #725657.

Maybe they should revert the patches which introduced that...

Btw: Who is expecting what? Why does upstream change the behaviour?

Expanding to absolute paths is totally bogus. I don't understand what kind of idiots from upstream came with that up as a default. It's total crap. For example, you cannot build particular .o files inside some build tree anymore. E.g. with kernel this used to work: make kernel/mo<TAB><BACKSPACE>o but now, it expands to mess. And there is another POV, the cosmetic one: $ cd /l/latest/repos/clang/lib/StaticAnalyzer $ ls Check<TAB> $ ls /l/latest/repos/clang/lib/StaticAnalyzer/Checkers/ This is a parse error for my brain. Should I complain to upstream, i.e. is this purely an upstream issue? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=752422 https://bugzilla.novell.com/show_bug.cgi?id=752422#c9 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freespacer@gmx.de, | |koenig@linux.de, | |lmuelle@suse.com --- Comment #9 from Dr. Werner Fink 2012-03-16 10:10:19 UTC --- (In reply to comment #7) This patch which had caused bug #725657 is within the official patches of the bash 4.2.8. Now for a fix the first version of the patch for the direxpand feature had been added due to the pressure of Harald Koenig. To make this work the shopt direxpand had to be enabled. Then I had several reports/rants that this fix breaks other completion features and the bash its self. Therefore I had disabled it again. After this I had been ranted by several other users wanted their `expected' behaviour back. Now with the final patch from the direxpand clone of the bash git repository it seems to work (even without shopt direxpand set). This was found out by Sebastian Siebert as he had report this upstream. Hopefully this patch will become part of the bash git repository at its head. You may vote upstream for the patch becoming part of the bash main line. Nevertheless you may also try the latest complete.bash see attachment #481767 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=752422 https://bugzilla.novell.com/show_bug.cgi?id=752422#c11 --- Comment #11 from Dr. Werner Fink 2012-03-16 11:13:35 UTC --- Without the final patch bug #725657 is not fixed. Then it may work for as `expected' for you but what about all the others which complains about not expanding variables on completion? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=752422 https://bugzilla.novell.com/show_bug.cgi?id=752422#c13 --- Comment #13 from Sebastian Siebert 2012-03-16 12:36:33 UTC --- Hi Werner, Jiri and all other. Could you take a look to an additional patch for the direxpand feature. http://lists.gnu.org/archive/html/bug-bash/2012-03/msg00040.html Regards, Sebastian -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=752422 https://bugzilla.novell.com/show_bug.cgi?id=752422#c15 --- Comment #15 from Dr. Werner Fink 2012-03-16 17:24:04 UTC --- I've already burnt my fingers with upstream patches ... now let's see whats happen and let's wait that my fingers will cool down. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=752422 https://bugzilla.novell.com/show_bug.cgi?id=752422#c18 --- Comment #18 from Jiri Slaby 2012-04-11 21:23:05 UTC --- I think we can close this, as it works fine now. Werner? -- 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.