Skip to content

Latest commit

 

History

History
29 lines (22 loc) · 1.28 KB

ADVANCED_CONFIGURATION.md

File metadata and controls

29 lines (22 loc) · 1.28 KB
Raw

Advanced Configuration

For hobbyists this might be interesting.

goenv init is the only command that crosses the line of loading extra commands into your shell. Coming from rvm, some of you might be opposed to this idea. Here's what goenv init actually does:

  1. Sets up your shims path. This is the only requirement for goenv to function properly. You can do this by hand by prepending ~/.goenv/shims to your $PATH.

  2. Installs autocompletion. This is entirely optional but pretty useful. Sourcing ~/.goenv/completions/goenv.bash will set that up. There is also a ~/.goenv/completions/goenv.zsh for Zsh users.

  3. Rehashes shims. From time to time you'll need to rebuild your shim files. Doing this on init makes sure everything is up to date. You can always run goenv rehash manually.

  4. Installs the sh dispatcher. This bit is also optional, but allows goenv and plugins to change variables in your current shell, making commands like goenv shell possible. The sh dispatcher doesn't do anything crazy like override cd or hack your shell prompt, but if for some reason you need goenv to be a real script rather than a shell function, you can safely skip it.

To see exactly what happens under the hood for yourself, run goenv init -.