Open waivek opened 1 month ago
I'm not sure exactly what you mean when you say "the fish completion script seems to be adding it's own startswith type check, thus overriding the custom validator." This is the code we're generating:
My guess would be fish's own machinery is filtering returned completions by prefix. I'm not familiar enough with fish to know if there's an option to change this. It's possible the shell simply doesn't allow it.
Code Sample for Reproduction:
To register completions on bash, I do
And for fish I run
On bash, when I type
./mycommand.py x<TAB>
I get:This is the desired result, that I would also like to get in my fish completion, however on fish I get:
Basically, no matches.
Upon more experimentation it seems that the fish completion script seems to be adding it's own
startswith
type check, thus overriding the custom validator.Is there a way to modify the generated fish completion script to remove this behavior?