-
-
Notifications
You must be signed in to change notification settings - Fork 672
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
[BUG] Completions that include colons get separated in zsh #162
Comments
I don't think this is a bug in typer, I think this is just the nature / default behaviour of the zsh completion system. zsh expects the results of your completetion function to take the form but I suspect this is beyond the scope of typer's zsh auto-completion support (I'm not a core contributor, i can't speak for them, this is just my two cents) |
@alextremblay I tried the snippet in the link but it didn't work.
but got I have no idea how zsh completion works, can you help me configure zsh so that the completions work? Thank you! |
@tddschn sadly, no. i think this is something that would need to change in typer's auto-generated zsh autocomplete script. you could try editing the generated script yourself, but then if you change your CLI's code and need to regenerate autocompletions, your changes will be wiped out |
Thanks @jaywonchung! This was handled by @snapbug in #988, the fix will be available in version 0.12.6 in the next hours. 🤓 🚀 |
Assuming the original need was handled, this will be automatically closed now. But feel free to add more comments or create new issues or PRs. |
Describe the bug
I have completions (via the
autocompletion
keyword argument in Arguments and Options) that include a colon (:
) in the string. In zsh, these completions get split into completion candidates and help texts at the colon.To Reproduce
main.py
with:When I cycle through the completion candidates, only
alpine
andnvidia/cuda
gets filled in.Environment
Additional context
I tried the exact same thing in Bash, and it worked as expected (the output in "But I expected it to output").
The text was updated successfully, but these errors were encountered: