Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • "I probably created bad symlink to vim"? Read your shell history and see exactly what you did do. Commented Dec 2, 2017 at 1:39
  • 1
    Are you sure that /usr/local/bin/vim is not just a hashed path? compare the output of type vim with that of which vim and execute hash -d vim if necessary. Commented Dec 2, 2017 at 2:02
  • 4
    also try running /usr/bin/vim, at least then we can be sure you actually have it properly installed. Then try ls -l /usr/bin/vim, if the first letter is l, you have overwritten your vim with a symlink somehow. Then show us what echo $PATH outputs and I guess double-checking if there is something fishy in /usr/local/bin/ won't hurt with ls -l /usr/local/bin/vim Commented Dec 2, 2017 at 2:15
  • I don't have Mac, but brew install vim to reinstall vim should capable fix automatically. Commented Dec 2, 2017 at 10:11