-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
Bug report: google-cloud-sdk fish completion instructions are wrong #30847
Comments
Ping @daenney. |
Hmm, that's annoying. So looking at my own installation of Google Cloud SDK from Cask I can indeed see that the
However, if I download one of the archives from https://cloud.google.com/sdk/downloads and extract it, they are there:
So it seems that somehow these are getting lost when Cask is installing them, after that causing issues with the I'm not really a maintainer of this though, I just landed the patch last time to ensure Fish users could get correct completion since it wasn't working for me. I don't really know how to go about figuring out why the |
Ah, the problem seem to stem from the following; the formula downloads the Cloud SDK from here: https://dl.google.com/dl/cloudsdk/release/google-cloud-sdk.tar.gz, to always get the latest release. However, that bundle, contrary to the versioned bundles at https://cloud.google.com/sdk/downloads doesn't contain the |
Description of issue
I installed the Google Cloud SDK cask and followed the install instructions for fish completions:
then tried running
fish_update_completions
.I got:
After removing those two lines from my fish config file, I was able to run
fish_update_completions
and got this correct looking result:It looks like the instructions in #9958 aren't valid anymore possibly?
I'm pretty sure that MANPATH should be set something like this, although it should also account for
MANPATH
not existing beforehand: fish-shell/fish-shell#2090Currently there is no help directory or manpage subfolder at that location, so that won't work at the moment, and this causes the error
No paths specified
.To summarise there are two problems here:
The text was updated successfully, but these errors were encountered: