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
complete: support json for complex arguments #10197
Comments
A longstanding issue is that serialized completions don't carry metadata.
Once we have flags we can add one to allow to disable coloring for individual completions.
I'd rather see a generalized improvement here (also we want to be somewhat honest about what will be inserted).
Hmm, we could add a text field (separate from the completion pager), that should work for both? |
True, but I don't think there is much room for improvement here without having additional context from the completion scripts.
Yes, that is how it is done it zsh: one multiline string with different coloring. |
So in carapace I've got data like this.
Would be nice if fish would provide a bit more control over the completion values.
What might work is accepting
json
additionally to thevalue\tdescription
format.Meaning: check if response starts with
{
and try to parse the result asjson
otherwise fallback to the default.Display
What to show during completion.
Fish currently truncates the value without knowing where to cut.
Style
How to highlight the displayed value (color, bold, underlined...).
Either a separate value or support ansi esscape codes for display.
Space Suffix
Some way to control if a space suffix shall be added.
E.g. when completing a command that is passed as string.
Error / Usage
Some way to show error and usage messages separate from the completion values.
Errors are currently embedded into the values as workaround.
Tags
Additional identifier for the values like
subcommand group
,files
,branches
to filter or group them.related #7832
The text was updated successfully, but these errors were encountered: