Summary: | bash completion unnecessarily escapes colon (:) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chris Boot <bootc> |
Component: | Current packages | Assignee: | Gentoo Shell Tools project <shell-tools> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | vzheiska |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Chris Boot
2004-10-11 07:21:23 UTC
I've also seen this with du, and I'm sure there's others ; I'll see if I can track this down today or tomorrow even though this is most likely an upstream bug. This is even worse with cdrecord. Reproducible: Always Steps to Reproduce: 1. Fire up a bash shell 2. Type "cdrecord blank" 3. Press <tab> to perform the completion 4. Delete the trailing space 5. Press <tab> to perform another completion Expected Results: It should have appeared as: "cdrecord blank" and should have displayed the possible options for the blank parameter. Tested with every bash-completion versions in portage from bash-completion-20040526 to bash-completion-20040711. I just emerged bash-completion-20040711 and the problem still occurs with this version. I've been trying to track this down... the only thing I can think of, is that bash is automatically escaping the ':' for some reason. I'm wondering if maybe there's an option you have to (un)set. I'll use chown for this example with my username, ka0ttic. # chown ka0<TAB> # chown ka0ttic\: Now, in the completion function, _chown(), the previous "use case" causes _chown() to execute 'compgen -S : -u -- $cur' where $cur is the first 3 letters I typed in before hitting <TAB>. Trying this manually on the command-line, shows that it doesn't escape the colon: # compgen -S : -u -- ka0 ka0ttic: ciaranm, do you know of what is causing bash to automatically escape the colon? Finally heard back from upstream; As I suspected, bash itself automatically escapes the colon, so there's not much we can do about it. *** Bug 107684 has been marked as a duplicate of this bug. *** |