News for hackers. Stuff that matters.

A comment on YouCompleteMe, a Fast, As-You-Type, Fuzzy-Search Code Completion Engine for Vim. Parent comment

Re:YouCompleteMe, a Fast, As-You-Type, Fuzzy-Search Code Com... by johncoltrane on Tuesday February 05, 2013 @05:07AM (#5169965)
For the typical use of Vim, it's perfect:

    $ vim filename
[ Parent | on HN ]
Re:YouCompleteMe, a Fast, As-You-Type, Fuzzy-Search Code Com... by jlgreco on Tuesday February 05, 2013 @10:20AM (#5171046)
It breaks down when you use it in other common ways, like from your git configuration.
[ Parent | on HN ]
Re:YouCompleteMe, a Fast, As-You-Type, Fuzzy-Search Code Com... by johncoltrane on Tuesday February 05, 2013 @10:42AM (#5171186)
You can't use

    vim
anyway in git: you must give it the full path.
[ Parent | on HN ]
Re:YouCompleteMe, a Fast, As-You-Type, Fuzzy-Search Code Com... by jlgreco on Tuesday February 05, 2013 @01:07PM (#5172115)
No, just 'vim' itself is fine, if you have a 'vim' in your PATH.

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).

[ Parent | on HN ]
Re:YouCompleteMe, a Fast, As-You-Type, Fuzzy-Search Code Com... by johncoltrane on Wednesday February 06, 2013 @03:31AM (#5175474)
No. 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.
[ Parent | on HN ]