4 ms·
An alias will only work with things that are using your shell with your configuration sourced. Things that merely use your PATH won't pick that up.
by jlgreco 14y ago
An alias will only work with things that are using your shell with your configuration sourced. Things that merely use your PATH won't pick that up.
- johncoltrane 14y agoFor the typical use of Vim, it's perfect: $ vim filename
- jlgreco 14y agoIt breaks down when you use it in other common ways, like from your git configuration.
- johncoltrane 14y agoYou can't use vim anyway in git: you must give it the full path.
- jlgreco 14y agoNo, just 'vim' itself is fine, if you have a 'vim' in your PATH. https://github.com/search?q=%27editor+%3D%27++extension%3A.gitconfig&type=Code&ref=searchresults https://github.com/search?q=%27editor+%3D%27++extension%3A.g... What I usually do is maintain a set of symlinks in ~/bin/ (which is in my PATH) if they are not already in my PATH (or if I want them to override something else in my PATH, like HEAD builds of various things on occasion), and only use aliases to set default arguments (`ls --color=auto` for example).
- johncoltrane 14y agoNo. On Mac OS X, using `vim` generally causes this error: error: There was a problem with the editor 'vi' The full path must be used to get rid of it.