#389111 autocompletion fails on non-printable characters in directories

Package:
zsh
Source:
zsh
Description:
shell with lots of features
Submitter:
David Madore
Date:
2012-12-20 23:15:03 UTC
Severity:
minor
#389111#5
Date:
2006-09-23 23:01:56 UTC
From:
To:
zsh seems to autocomplete non-printable characters by representing
them as something like $'\377', but then it fails to understand them
when autocompleting one further level of directories.

For example, suppose we start in an empty directory (/tmp/test, say)
and use no config file at all (cd /tmp/test; HOME=`pwd` zsh), just to
make sure we load only the base completion module: then try

% export LC_ALL=C
% mkdir "`/usr/bin/printf 'x\\377z'`"
% touch "`/usr/bin/printf 'x\\377z'`"/corge
% cat x$'\377'z/

It will complete so far (if you type x<TAB>, it completes to
x$'\377'z/ as shown above), but no further (the "corge" part never
appears).

#389111#8
Date:
2006-09-24 01:42:28 UTC
From:
To:
x$'\377'z is getting munged to "x$\\377z" and then matching
[^][*?#^\|\<\>\\]#(\`[^\`]#\`|\$)*/* in _path_files.