Indrajit Raychaudhuri c4bc93d921 command-not-found: Detect Homebrew repo internally, not idiomatically For performance reasons, we prefer detecting Homebrew prefix internally instead of the more idiomatic form `brew --repository`. We attempt looking up $HOMEBREW_REPOSITORY first (in case `brew shellenv` has been sourced-in earlier). Else, we look it up by resolving absolute path of $HOMEBREW_REPOSITORY. This should work for most standard (and officially documented) Homebrew installations.	3 years ago
..
README.md	general: Update documentation better qualifying runcom paths	4 years ago
init.zsh	command-not-found: Detect Homebrew repo internally, not idiomatically	3 years ago

Indrajit Raychaudhuri c4bc93d921 command-not-found: Detect Homebrew repo internally, not idiomatically

For performance reasons, we prefer detecting Homebrew prefix internally
instead of the more idiomatic form `brew --repository`.

We attempt looking up $HOMEBREW_REPOSITORY first (in case `brew shellenv`
has been sourced-in earlier). Else, we look it up by resolving absolute
path of $HOMEBREW_REPOSITORY.

This should work for most standard (and officially documented) Homebrew
installations.

3 years ago

README.md

general: Update documentation better qualifying runcom paths

4 years ago

init.zsh

command-not-found: Detect Homebrew repo internally, not idiomatically

3 years ago

README.md

Command-Not-Found

When you try to use a command that is not available locally, searches the package manager for a package offering that command and suggests the proper install command.

Debian and Arch Linux based distributions use the command-not-found tool.

macOS uses Homebrew's command-not-found clone. Note that unless you have a recent version of Homebrew installed, you might also need to tap the command-not-found Homebrew repository following the instructions.

Authors

The authors of this module should be contacted via the issue tracker.