Re: Reading difficult directory name correctly:

[Ray Andrews <rayandrews@eastlink.ca>]

On 2020-12-10 2:32 p.m., Bart Schaefer wrote:

I added this to the bottom of my config file:

     ###
     #autoload -U compinit && compinit -d $ZSHBOOT/zcompdump
     autoload -U compinit -D && compinit -d $ZSHBOOT/zcompdump
     zstyle '*' format %d

... and it made no difference.  First TAB gives the partial completion.  
Second TAB adds the

     Completing `file'

message, but nothing is added -- no files are offered nor is the partial 
line completed.


> A file will be written with a backtrace of what the completion system
> did.  An entry is made in the shell history providing the name of the
> file.
Yikes, it's 420 lines long :(

This auto created directory is the only case I know of where anything 
like this happens so it's hardly a big deal in practice, still I'm 
curious, but don't waste any time on it Bart.

One more experiment: no changes to config but:

     7 /aMisc 5 $ zsh -f
g5--9-Debian1#
     g5--9-Debian1# rm Sky\ above\ 49°30\'N\ 123°30\'W\ at\ Fri\ 2020\ 
Dec\ 11\ 0\ 58
     Sky\ above\ 49°30\'N\ 123°30\'W\ at\ Fri\ 2020\ Dec\ 11\ 0\ 58.html
     Sky\ above\ 49°30\'N\ 123°30\'W\ at\ Fri\ 2020\ Dec\ 11\ 0\ 58_files/

So, it works as you described -- second TAB shows both the file and the 
directory and completion cycles thru them.

So I broke something.