[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Strange autocompletion behavior using PATH variable with special symbol
From: |
Ilyushkin Nikita |
Subject: |
Strange autocompletion behavior using PATH variable with special symbol - apostroph (') |
Date: |
Sat, 08 Feb 2014 22:04:28 +0400 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 |
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash'
-DSHELL -DHAVE_CONFIG_H -I. -I../bash -I../bash/include
-I../bash/lib -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall
uname output: Linux Lenovo-ThinkPad-T61 3.11.0-15-generic #25-Ubuntu SMP
Thu Jan 30 17:25:07 UTC 2014 i686 i686 i686 GNU/Linux
Machine Type: i686-pc-linux-gnu
Bash Version: 4.2
Patch Level: 45
Release Status: release
Description:
Expanding PATH variable influence word completion, based on whether
was apostrophes in additional path or not.
Repeat-By:
I have an executable file (called deadbeef) with appropriate
executable rights, the path to which contains 2 apostrophes:
/home/mallniya/hard'n'soft/soft/gnu-linux/portable/deadbeef-0.6.0
Specialy for an experiment I put the same file into another directory:
/home/mallniya/hardnsoftaa/soft/gnu-linux/portable/deadbeef-0.6.0
If I export first path to the variable PATH there will be no
autocompletion in bash, but there will be in the second case.
When I type in terminal first letters of program, that resides in
exported directory:
dead[TAB]
There is no completion in first case, but when I use TAB with the
same word in second condition (where there is no ' in the PATH) - it works.
But if I type command deadbeef in first case manually - it also
executes.
Moreover, both which and type commands tell, that the executable
file is exists in both cases.
I tried to report it as bash-autocompletion bug, and that's what
they said:
"Seems that we (bash-completion) have nothing to do with this;
plain vanilla bash behaves as described. See "BUG REPORTS" in the bash
man page if you wish to report it against bash."
So I'm here.
Original post:
http://askubuntu.com/questions/415043/strange-autocompletion-behavior
Fix:
[Description of how to fix the problem. If you don't know a
fix for the problem, don't include this section.]
- Strange autocompletion behavior using PATH variable with special symbol - apostroph ('),
Ilyushkin Nikita <=