I'm a fish user, and I'm new to caparace
I followed the step describe in https://carapace-sh.github.io/carapace-bin/setup.html
I was surprised to see
carapace --list | awk '{print $1}' | xargs -I{} touch ~/.config/fish/completions/{}.fish # disable auto-loaded completions (#185)
see
I can see the reference here
carapace-bin/docs/src/setup.md
Line 32 in 1b1ecb1
I found the code was moved via 6ad36ab and was initially added via 79e988e (via #880)
All these are pretty old, the #185 was mentioning
Is there any progress around this ?
I saw the status of fish-shell#6716 but I was curious if there is nothing else that evolved in the last few years. I find pretty painful to create empty file it's a strange logic
I found this cli/cli#360 (comment)
I would have expected carapace to:
create the empty file via the go, not via an shell rule
the empty file could have a better content than simply being empty
they could contain comment about why the file is there and empty
use fish "complete -e" can't help ?
maybe the fish file could contain the complete command instead of being empty
for example
~/.config/fish/completions/git.fish could contain this
complete -e 'git'
complete -c 'git' -f -a '(_carapace_lazy git)'
I might be wrong about the things I'm asking or the point I'm raising, but I would like to know if we couldn't do something better for the fish integration
Thanks
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too