Well...I'm so confused, cause the only real problem in my case is freaking apostrophe (').


Situation: expanding PATH variable influence word completion, based on whether was apostrophes in additional path or not.


Example: I have an exe file (called "deadbeef") with appropriate exe rights, which path 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 to the

/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 will be in a second case. When I type in terminal first letters of program in exported directory

dead [TAB]

There is no completion in first case, but when I use TAB with the same word in second condition - it works.

But if I type command "deadbeef" in first case manually - it also executes.


Moreover, both which and type commands tells, that exe file is existed in both case.


So what's the problem??? Why bash process the apostrophes like this?