Path: csiph.com!aioe.org!news.glorb.com!usenet.stanford.edu!not-for-mail From: deterenkelt.github@gmail.com Newsgroups: gnu.bash.bug Subject: Troubles with autocompletion of filenames with square brackets Date: Fri, 10 Jul 2015 10:36:52 +0300 Lines: 52 Approved: bug-bash@gnu.org Message-ID: NNTP-Posting-Host: lists.gnu.org X-Trace: usenet.stanford.edu 1436534304 31301 208.118.235.17 (10 Jul 2015 13:18:24 GMT) X-Complaints-To: action@cs.stanford.edu To: bug-bash@gnu.org Envelope-to: bug-bash@gnu.org X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 77.243.108.114 X-Mailman-Approved-At: Fri, 10 Jul 2015 09:18:23 -0400 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: aioe.org gnu.bash.bug:11168 Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: x86_64-pc-linux-gnu-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I./include -I. -I./include -I./lib -DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' -DSTANDARD_UTILS_PATH='/bin:/usr/bin:/sbin:/usr/sbin' -DSYS_BASHRC='/etc/bash/bashrc' -DSYS_BASH_LOGOUT='/etc/bash/bash_logout' -DNON_INTERACTIVE_LOGIN_SHELLS -DSSH_SOURCE_BASHRC -march=corei7-avx -O2 -pipe -fomit-frame-pointer --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=6144 uname output: Linux home 3.16.6-geek-i5 #11 SMP PREEMPT Fri Jul 3 19:54:14 MSK 2015 x86_64 Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz GenuineIntel GNU/Linux Machine Type: x86_64-pc-linux-gnu Bash Version: 4.3 Patch Level: 39 Release Status: release Description: Autocompletion fails for files starting with an opening square bracket and having closing bracket somewhere in the filename. Repeat-By: $ mkdir temp && cd temp $ mkdir -p one/{\[bad\]\ folder,\[yet\]\ another\ bad\ folder} Now try $ cd one # cd one/\[ ← should appear $ mkdir -p \[one\]/{\[bad\]\ folder,\[yet\]\ another\ bad\ folder} Type $ cd [ # cd \[one\]/ ← should appear $ cd \[one\]/ ← further completions do not work $ mkdir -p \[two\]/{\[bad\]\ folder,\[yet\]\ another\ bad\ folder} $ cd [ # cd \[ ← should appear $ cd \[t # ← doesn’t work. $ cd \[tw # ← doesn’t work. $ cd \[two # ← doesn’t work. $ cd \[two] # ← doesn’t work. $ cd \[two\] # ← doesn’t work. But if you type $ cd [two # cd \[two\]/ ← should appear Surprise — this works! However… $ cd \[two\]/ # ← no further completions work :( Fix: [Description of how to fix the problem. If you don't know a fix for the problem, don't include this section.]