https://bugzilla.novell.com/show_bug.cgi?id=752422 https://bugzilla.novell.com/show_bug.cgi?id=752422#c7 --- Comment #7 from Jiri Slaby <jslaby@suse.com> 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.