zsh escapes space after singleton completions about argcomplete HOT 8 CLOSED

To be honest, I don't recall the exact reason why I started using nospace and whether it still holds. I'll need to play around with it and see if anything breaks...

from argcomplete.

Sorry about the multiple commits. I'm new to git and github. But what I submitted seems to work fine under both bash and zsh. The bash version I used is 4.2.37 (also listed in the log for f6c89aa).

Thanks for looking in to this!

from argcomplete.

See #55, thanks

from argcomplete.

As mentioned in #82, removing -o nospace interferes with the ability to return singleton completions that may be partial (e.g. a directory name followed by a slash, which the user might choose to use as is or expand to the directory's contents). Re-titling the bug to concern zsh specifically.

from argcomplete.

Does it make sense to have "singleton completions that may be partial"? In the case of a directory name followed by a slash, should you not also return the contents of that directory? For example, if you return dir/ and expect the user could use something in that directory, why not also return dir/subdir/, dir/file, etc?

from argcomplete.

Yes, it does. Try completing a path of several directories in bash. Even if there is a unique completion, each <TAB> will yield just one directory completion at a time. That's an intentional UX design, and I'd like to conform to it.

from argcomplete.

More generally, we can't reasonably return all completions in a tree hierarchy.

from argcomplete.

What I had assumed was happening is that when a directory would be returned as the only match, it also returned the contents of that directory, eg dir/ and dir/subdir (but not dir/subdir/file or any deeper in the hierarchy), which would cause dir/ to be filled in as the common prefix. However you are correct - even when show-all-if-ambiguous is turned on, bash will not display the contents of a directory until tab is pushed a second time.

from argcomplete.