Your message dated Sat, 23 Sep 2006 21:42:28 -0400
with message-id <[EMAIL PROTECTED]>
has caused the Debian Bug report #389111,
regarding autocompletion fails on non-printable characters in directories
to be marked as having been forwarded to the upstream software
author(s) [EMAIL PROTECTED]
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
> 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).
x$'\377'z is getting munged to "x$\\377z" and then matching
[^][*?#^\|\<\>\\]#(\`[^\`]#\`|\$)*/* in _path_files.
--- End Message ---
