-
Notifications
You must be signed in to change notification settings - Fork 367
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
generated completion invalid for fish shell #821
Comments
Hey @nate-duke looking into the issue further - I was able to get the same output in fish as you listed above, but when I replaced your outer single quotes with double quotes, I don't get an error. complete -c gum -f -n "__fish_seen_subcommand_from choose" -x -l selected -d "Options that should start as selected (selects all if given '*')" Can you please let me know if this command works as expected for you? Thanks! |
yes @bashbunni that works. That's exactly what i did to make my shell load without error. I just wasn't certain what would have to be done in the source e.g: Line 18 in 3745655
to result in double quotes in the generated completion files. Also, to be clear the use of the asterisk in those two places in the referenced pull requests are problematic, at least for the generated fish shell completions. |
thanks @raphamorim! could you take a look at Line 23 in bb9fee7
|
Sure! Will do a PR, thank you @nate-duke |
Describe the bug
A recent change rendered the generated completion files for the fish shell with a quoting issue. The issue is a pair of single quotes around an asterisk.
complete -c gum -f -n '__fish_seen_subcommand_from choose' -x -l selected -d 'Options that should start as selected (selects all if given '*')'
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No parsing errors in completion scripts.
Screenshots
Desktop (please complete the following information):
Additional context
I looked around the completion generation code in the repo but can't pinpoint exactly what changed or where a fix could be performed. I'm not terribly familiar with the codebase.
The text was updated successfully, but these errors were encountered: