You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see that the json generated by carapace gh powershell a has a trailing space in its CompletionText. Since there is a char in the string that needs to be escaped, FZF puts quotes around it for a literal.
The trailing space is visible by doing:
carapace.exe gh powershell a |ConvertFrom-Json|Select-Object-First 1-ExpandProperty CompletionText |Select-String-Pattern .*
This functionality seems like it is intentional, but I am not able to find exactly where in the code (or spec) that this is happening. A configuration option to disable or set the trailing options would be amazing.
Polar
The text was updated successfully, but these errors were encountered:
Yes, this is an intentional feature for fluent completion and one of the things powershell doesn't do well.
I can understand though how the inconsistency can be disrupting and adding this is fairly easy.
Current Behavior
When doing a completion, there is a trailing space.
Expected Behavior
Native completions do not include a space in powershell, even on flag completions. I would expect carapace to be idiomatic with these.
Steps To Reproduce
gh a <TAB>
gh "alias "
Version
1.0.7
OS
Shell
Anything else?
I can see that the json generated by
carapace gh powershell a
has a trailing space in itsCompletionText
. Since there is a char in the string that needs to be escaped, FZF puts quotes around it for a literal.The trailing space is visible by doing:
This functionality seems like it is intentional, but I am not able to find exactly where in the code (or spec) that this is happening. A configuration option to disable or set the trailing options would be amazing.
Polar
The text was updated successfully, but these errors were encountered: