Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
requires #130
this PR installs shell completions using homebrew post install hooks and provides instructions on how to install them as install.sh output.
complexities:
eval "$(brew shellenv)"
in their zshrc, we can write to$(brew --prefix)/share/zsh/site-functions
pretty blindlybecause it's complex to detect what zsh/bash setups a given installer has from inside the installer script, we instead have the install script tell users both the "dumb" rc-centric way to install, and the most common "managed" way.
one alternative approach that folks have talked about is putting this in a
cu init
subcommand or similar. we could do that, but it has all the same difficulties that come with putting this in autoinstalling from our bash-specific install script. there are too many possible shells, userspace package managers, and plugin frameworks and custom configurations (including the absence of them).NOTE: i haven't tested the homebrew tap, don't merge this without testing it on a fork