It is now 2022, over a decade later and this annoying bug still exists.
Ubuntu 21.10
bash 5.1.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778627
Title:
bash completion now quotes shell
** Tags removed: natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778627
Title:
bash completion now quotes shell variable references rather than
expanding them
To manage notifications about
I still get \$HOME when pressing Tab in bash 5.0 & 5.1 (ubuntu 20.4)
Can the bug we reopened?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778627
Title:
bash completion now quotes shell variable
(corrected)
Agreed, this is an annoying bug and has been around far too long (a decade?).
ls $HOME/.ss should give: ls $HOME/.ssh/
"shopt -s direxpand" expands $HOME which is not wanted.
"shopt -u complete_fullquote" should give me what I want but has no effect.
--
You received this bug
Agreed, this is an annoying bug and has been around far too long (a
decade?).
ls $top/.ss should give: ls $HOME/.ssh/
"shopt -s direxpand" expands $HOME which is not wanted.
"shopt -u complete_fullquote" should give me what I want but has no effect.
--
You received this bug notification because
It's now 2021 - I'm on Ubuntu 20.04.2 LTS and I'm still being annoyed
by this bug!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778627
Title:
bash completion now quotes shell variable references
I strongly agree with thava (in comment #51).
It's now 2017 and this issue is still unresolved and continues to
require a sub-optimal workaround and no proper fix returning the
original behaviour and allowing the variable name to remain in the
command-line, post tab-completion.
--
You received
If the proposed fix requires setting direxpand variable, then that is
not a fix, it is a workaround fix. (something is better than nothing
though). Historical behaviour should not be changed and users must not
be expected to set this new variable. This is affecting so many people
and this is real
I'd just like to chime in and say, whoever had the bright idea of
escaping $ during tab completion... go to hell.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778627
Title:
bash completion now
Any idea why `ls $d/f[TAB]` still becomes `ls \$d/f `? Other commands seem
fine, but not `ls`.
Does anyone also have the same problem after update? I'm running Precise, btw
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ladios,
just updated my precise installation to the latest bash package and now it
works as expected.
Including ls.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778627
Title:
bash completion now
Investigated. All the commands that failed to do completion properly are
defined with `-F _longopt`.
dpkg-query shows me that there are a lot of conffiles... OMG I wonder how many
they are throughout my installation.
Will try to get rid of those conffiles to see if that fixes my problem.
--
Oh... I thought conffiles is short for conflict files... lol
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778627
Title:
bash completion now quotes shell variable references rather than
expanding
Actually, most defined completions would add '\' in front of '$'. It only works
when the command has no completion defined, for instance, the `ll` alias does.
Don't know what went wrong. I think I have to go for the direxpand option.
--
You received this bug notification because you are a
On 10 April 2013 14:48, Ladios Jonquil 778...@bugs.launchpad.net wrote:
Actually, most defined completions would add '\' in front of '$'. It only
works when the command has no completion defined, for instance, the `ll`
alias does.
Don't know what went wrong. I think I have to go for the
Yes, I enabled direxpand option eventually. It works.
I misunderstood this update. I thought this would actually fix the shell
variables quoting issue (by not quoting them), but it didn't.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- In natty, bash completion now quotes shell variable references rather than
expanding them
+ bash completion now quotes shell variable references rather than expanding
them
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This bug was fixed in the package bash - 4.2-2ubuntu2.1
---
bash (4.2-2ubuntu2.1) precise-proposed; urgency=low
* Fix directory expansion. (LP: #778627)
-- Alec Warner anta...@google.com Mon, 18 Mar 2013 22:12:54 +
** Changed in: bash (Ubuntu Precise)
Status: Fix
Finally, this bug is fixed!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778627
Title:
bash completion now quotes shell variable references rather than
expanding them
To manage notifications
19 matches
Mail list logo
