Your message dated Sun, 2 Dec 2018 11:54:02 -0200
with message-id <[email protected]>
and subject line Re: bash-completion: Fails to complete after quotes.
has caused the Debian Bug report #576390,
regarding bash-completion: Fails to complete after quotes.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
576390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576390
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bash-completion
Version: 1:1.1-3
Severity: normal
Hello,
quotes confuse bash-completion, and I don't think they should. For
example:
$ mkdir "p's"
$ touch p\'s/test
$ ls p\'s/
Here TAB fails to complete to test. The same happens with double
quotes:
$ mkdir 'p"s'
$ touch 'p"s'/test
$ ls p\"s/
If both folders exist, something even more surprising happens:
$ ls p\"
Pressing TAB, I would expect this to complete to p\"s, but instead the
trailing \" is removed, and both folders are presented as possible
completions.
Philipp
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (600, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bash-completion depends on:
ii bash 4.1-2 The GNU Bourne Again SHell
bash-completion recommends no packages.
bash-completion suggests no packages.
-- no debconf information
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
On Sat, 3 Apr 2010 22:52:29 -0400 Philipp Weis <[email protected]> wrote:
>
> $ mkdir "p's"
> $ touch p\'s/test
> $ ls p\'s/
>
> Here TAB fails to complete to test. The same happens with double
> quotes:
With current bash-completion, this works correctly:
$ ls p\'s/[TAB]
$ ls p\'s/test [CURSOR]
> $ mkdir 'p"s'
> $ touch 'p"s'/test
> $ ls p\"s/
Likewise:
$ ls p\"s/[TAB]
$ ls p\"s/test [CURSOR]
> If both folders exist, something even more surprising happens:
>
> $ ls p\"
>
> Pressing TAB, I would expect this to complete to p\"s, but instead the
> trailing \" is removed, and both folders are presented as possible
> completions.
Likewise:
$ ls p\"[TAB]
$ ls p\"s/[CURSOR]
This bug is similar to bug #557366 and the fix is probably the same,
i.e. provided by the following upstream commit (newer than version 1.1):
https://github.com/scop/bash-completion/commit/c9c98da36edeb9305e24e7ea2d8ccf8b0934ce70
I'm closing the bug, but please do not hesitate to reopen it if you
have more information.
--- End Message ---
