-
Notifications
You must be signed in to change notification settings - Fork 420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autocomplete mishandling suggestions with spaces #1754
Comments
Thank you for raising this! Will you be able to provide a pull request for this? |
It's on Bash / Zsh. By the time For what I've seen, escaping here doesn't help, but there are some workarounds… I may give it a go with a PR, but will let you know if I run into trouble. |
- Both positional params and option candidates are now stored in the autocomplete script as an array. - By setting `IFS=$'\n'` for those scenarios, each array entry is treated as a single candidate, allowing to honor any spaces in the original suggestions coded by the user.
When an option provides a
completionProvider
that list strings with spaces, the autocomplete doesn't honor the completion provider, but instead splits all options on its own.For instance, given the example:
I'd expect 3 candidates to be offered, with proper escaping for the whitespace. However, this is what it's actually being suggested:
5 options, all single words, duplicates removed.
The text was updated successfully, but these errors were encountered: