*** This bug is a duplicate of bug 752193 ***
https://bugs.launchpad.net/bugs/752193
Hi, same problem, which reading this trend I realise appeared just after
I installed acrobat reader. The sed workaround + rebooting made the job.
Thanks!
--
You received this bug notification because you are
*** This bug is a duplicate of bug 752193 ***
https://bugs.launchpad.net/bugs/752193
Sorry, it do has been fixed.
I got this issue because I add a third-party completion script.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
My system was installed from beta2 livecd.
But I don't have /etc/bash_completion.d/acroread.sh, and I didn't install
adobereader-enu package either.
What can I do to fix the problem?
Tks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
*** This bug is a duplicate of bug 752193 ***
https://bugs.launchpad.net/bugs/752193
It has been fixed in the latest acroread:
acroread (9.4.2-0natty1) natty; urgency=low
* Not allowing the autocompletion script to redefine _filedir as it was
causing problems with the proper autocompel
apt-get remove adobereader-enu solved it for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/716008
Title:
strange bahavior on directory completion with bash built-in commands
--
ubuntu-bugs mai
I also had the same problem, confirming that the sed workaround works
fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/716008
Title:
strange bahavior on directory completion with bash built-in co
I also suffered from this bug, and after some discussion in #bash and
#ubuntu+1, figured out the right search terms to figure this out.
The sed workaround works fine here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
On Sun, Apr 10, 2011 at 05:09:30PM -, Bram Swenson wrote:
> The sed workaround worked perfectly for me as well.
---end quoted text---
Removing acroread fixed that indeed !
--
أحمد المحمودي (Ahmed El-Mahmoudy)
Digital design engineer
GPG KeyID: 0xEDDDA1B7
GPG Fingerprint: 8206 A196 2084
The sed workaround worked perfectly for me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/716008
Title:
strange bahavior on directory completion with bash built-in commands
--
ubuntu-bugs
The workaround works properly: it is a bug in acroread package, not in
bash-completion package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/716008
Title:
strange bahavior on directory completion w
> and it works
Indeed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/716008
Title:
strange bahavior on directory completion with bash built-in commands
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
This turn out be to a bug in acroread package.
http://aur.archlinux.org/packages.php?ID=16980
The workaround is
sed -i "s/_filedir/_filedir_acroread/" /etc/bash_completion.d/acroread.sh
and it works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: bash-completion (Ubuntu)
Importance: Undecided => High
** Changed in: bash-completion (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/71600
This new behaviour is horrible
** Changed in: bash-completion (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/716008
Title:
strange bahavior on directory comp
This is due to changes in the 1.3 upstream version of bash-completion I
think. In the diff there is some talk about dynamically toggling "-O
filenames".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/71
15 matches
Mail list logo
