-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Probably user stupidity, but it doesn't seem to work? #34
Comments
The messages in the status area are normal and cannot be avoided. You need to have a vim filetype set to something before getting the completion. If you just try to edit an empty file, its filetype will be set to 'text' and YCM ignores that filetype on purpose. |
Same issue here, but filetype is already set to "cpp". Any idea? |
People find it annoying. It's easy for the user to add this if it's not the default, but impossible to remove it if it is the default. Fixes ycm-core#34
Hey, Why was this issue never addressed? I am having the same issue. No matter what kind of file I try to edit, it just says "^X mode (^]^D^E^F^I^K^L^N^O^Ps^U^V^Y)" at the bottom and no autocomplete suggestions are given. Please help. |
It is a strange issue, I have vim with YCM on my macbook and never had issue But the vim with YCM in my RHEL dev server has this issue. |
My ycm works well before I update my plugins with "BundleInstall!" and recompile it. Then, I also encounter this problem, I do it with my desktop and laptop, however, they display different results. |
I've installed MacVim, symlinked mvim properly so I get to use the correct vi version in terminal. I've installed Vundle, and added the default required things, plus YouCompleteMe into ~/.vimrc
I've done the
:BundleInstall
, and it installed correctly. Built ymc, and was told it was installed successfully. But when I start using vim to type, I get these at the status area:No auto complete box or anything coming up.
For reference,
vim --version
shows:VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Dec 12 2012 16:22:25)
The text was updated successfully, but these errors were encountered: