fixes the instructions to enable autocompletion in zsh #5859
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
neersighted
approved these changes
Jun 16, 2022
Merged
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This change to the documentation fixes the instructions to enable autocompletion in zsh shells. See the description of the solution in the comment here: https://superuser.com/q/1718843.
Basically, if you add only this
to your
~/.zshrcfile, the autocompletion doesn't work and you also get an error thatcompinitis not a command. This happens in Mac OS Monterey (12.3.1). I am not familiar withcompinit, but I assume that this commit fixes this issue for all users (it fixed it for me and the user that asked that question, at least). It's possible that this issue has been raised before (but I didn't find a duplicate yet).