[Bug 933077] Re: completion for paths are bad in precise

2012-02-15 Thread Thomas C.
*** This bug is a duplicate of bug 769866 *** https://bugs.launchpad.net/bugs/769866 ok sorry - it is a acroread problem ... I also removed the symlink acroread.sh from /etc/bash_completion.d/ to /opt/Adobe/Reader9/Resource/Shell/acroread_tab restarted the shell and now it works right I had

[Bug 933077] Re: completion for paths are bad in precise

2012-02-15 Thread Thomas C.
ok.. the topic is listed also in bug #769866 but this bug report is for acroread - not for bash. I dont think that my problem has something to do with acroread -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.ne

[Bug 933077] Re: completion for paths are bad in precise

2012-02-15 Thread Thomas C.
ok, my last commend is also listed in bug #883268 But not the one from the topic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933077 Title: completion for paths are bad in precise To manage noti

[Bug 933077] Re: completion for paths are bad in precise

2012-02-15 Thread Thomas C.
a other bad example is the following: when a folder has a bank the \ in folder name get removed: thats how it looks current: "$ ls test folder\" thats how it should look (and was before): "$ ls test\ folder\" Its got also changed in precise -- You received this bug notification because you ar

[Bug 933077] Re: completion for paths are bad in precise

2012-02-15 Thread Thomas C.
** Description changed: In a bash shell after use the TAB key for extend a path, the path folder - name get extended with a blank key: + name get extended with a blank: "$ ls /etc " so you have first to use the backspace key to delete the blank and than enter / to continue in path in