Your message dated Tue, 27 Nov 2018 21:24:26 -0200 with message-id <20181127212426.2558a...@vostok.lan> and subject line Re: bash-completion: Doesn't complete filenames in a folder with quote symbols. has caused the Debian Bug report #557366, regarding bash-completion: Doesn't complete filenames in a folder with quote symbols. 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 ow...@bugs.debian.org immediately.) -- 557366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: bash-completion Version: 1:1.1-3 Severity: normal Folder names with quotes confuse bash-completion. $ mkdir a\'b $ touch a\'b/test $ cp a\'b/ The completing for the cp (or ls, mv, ...) parameter hangs after the first folder name and doesn't complete to the filename. Interestingly, it works with commands unknown to bash-completion. $ ll a\'b/test $ xyz a\'b/test work just fine. Philipp -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (600, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-svn14611 (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.0-7 The GNU Bourne Again SHell bash-completion recommends no packages. bash-completion suggests no packages. -- no debconf information -- Philipp Weis
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---On Sat, 21 Nov 2009 13:52:48 -0500 Philipp Weis <pw...@pweis.com> wrote: > Package: bash-completion > Version: 1:1.1-3 > Severity: normal > > Folder names with quotes confuse bash-completion. > > $ mkdir a\'b > $ touch a\'b/test > $ cp a\'b/ I tested this agains current bash-completion and it no longer reproduces the problem: $ mkdir a\'b $ touch a\'b/test $ cp a\'b/[TAB] $ cp a\'b/test [CURSOR] I believe that the following commit (newer than version 1.1), is the responsible for the fix: 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 ---