How to change the path of vim command

Use aliases.

Aliases are defined in one of your BASH RC files ~/.bashrc. Below, if it /usr/local/bin/vim's a symlink, create an alias called vim.

if [ -h '/usr/local/bin/vim' ]; then
    alias vim='/usr/local/bin/vim'
fi

The same logic can be applied as follows.

[ -h '/usr/local/bin/vim' ] && alias vim='/usr/local/bin/vim'

• -hTest if the file is a symlink, which might be the case when using Homebrew.
• -xTest if the file is a regular executable.

( The file is determined to be a link when ls -lthe first letter of its permissions is displayed as the letter l in l rwxr-xr-x .)

It may also be necessary to set several variables that the program uses to invoke the default editor.

EDITOR='/usr/local/bin/vim'
VISUAL='/usr/local/bin/vim'

After adding the definition to your shell's RC file, provide the source of the RC file to use the file or whatever new alias is source ~/.bashrcappropriate for your BASH configuration . command, command -v vimshow aliases are created when their output is as follows.

alias vim=/usr/local/bin/vim

Both versions use the same VIM RC file vim.

The advantage of pointing to a symlink instead of a binary executable is that aliases don't need to be updated on every MacVim upgrade. brew update && brew upgradeFor example, Homebrew will keep the symlinks pointing to the correct binary executables when upgrading using .

The system version /usr/bin/vimshould remain the same. It cannot be removed or changed anyway without disabling System Integrity Protection (SIP). The system version can still be used by typing /usr/bin/vim, however, viminvokes /usr/local/bin/vim.

Modify the path.

Another way to make all software installed through Homebrew available is to modify PATHso that all software installed by Homebrew comes first in Windows PATH. First, you need to know which zshRC file already contains the definition of the path.

cd
grep path .z*

One of the results may include fpath. This is not the correct variable. We are looking for a lowercase variable named path. After inferring the filename to edit, possibly ~/.zshrcor ~/.zprofile, then change the value of the pathvariable . For example, paththe following defines /usr/local/binand /usr/local/sbinfirst defines a script or program in the home directory, and last defines the rest of the system-defined path.

path=(
    /usr/local/{bin,sbin}
    $HOME/bin
    $path
)

The resulting Unix PATHvariables are then defined as follows.

/usr/local/bin:/usr/local/sbin:/Users/$username/bin:/usr/bin:/bin:/usr/sbin:/sbin

In zsh pathand Unix PATHvariables are "bundled" typseset, so as long as it is a file variable sourcethat is modified by editing : , eg. Then look at the variable to see if it has been modified as expected: .pathsource ~/.zprofilePATHecho $PATH

The maintainers of Homebrew packages are very good at figuring out which software is causing a problem with macOS (if it /usr/local/bincame first) /usr/bin. For example, if Homebrew were to install GNU id, the name of the software /usr/local/binwould be to avoid problems in gidBSD .id/usr/bin