-
Notifications
You must be signed in to change notification settings - Fork 177
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
Pixi fish completion breaks fish-native completion #1906
Comments
Yeah you are right, this has recently changed. But how do you want the completion to function? Because python being completed was more of a side-effect, probably because it was on your global path? |
The problem is that the auto-completion always completes the tasks, even if there is already a task. |
Also, I always want Edit: although I understand the decision to only show tasks. But it would be nice to complete both tasks and binaries in the envs' PATHs. How do other package managers do this? |
Yeah, let me see if we can work around this later. Does this not do this for |
It doesn't seem to behave the same:
|
We should take a look at the auto-completion after the first completion. But we don't autocomplete more than just until there is an actual solution to dynamic completion in |
Checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pixi, using
pixi --version
.Reproducible example
Type
Options offered by fish (my Pixi tasks):
Issue description
Since a recent release of Pixi the completions for fish hinder fish from using proper completion for anything that's not a Pixi task. This includes the lack of filename completion, see example above. Completions offer only Pixi tasks even in places where it doesn't make sense (see example above).
Expected behavior
Should allow filename completion and task name completion only in places where a task is expected.
The text was updated successfully, but these errors were encountered: