Enhancement: Option to Disable Warning Messages

[xanderdunn]

YouCompleteMe spits out a lot of warning messages to the user.

It will warn me if I start vim and don't have the the ycm support libs built every time I start vim. What if I'm aware of this and I'm fine with not having the libraries built right now?

It will warn me if I open a C/C++/C#/ObjC file with no .ycm_etra_conf.py in the directory. I see this incessantly. I'm going to be opening .cpp files in various projects where I don't have a conf set all the time.

It will warn me if the file I'm opening is too large for it to process. So what? Don't bother me about it.

I would really like an option to tell YouCompleteMe to shut up. There's always :messages, and if I tell YouCompleteMe I know what I'm doing then it ought not annoy me.

[vheon]

I would really like an option to tell YouCompleteMe to shut up. There's always :messages, and if I tell YouCompleteMe I know what I'm doing then it ought not annoy me.

Is it possible in vim? To my knowledge there is no way to put a message in :messages but not display it first to the user. I just tried:

autocmd VimEnter * :silent echo "silent echo"
autocmd VimEnter * :silent! echo "silent! echo"
autocmd VimEnter * :silent echomsg "silent echomsg"
autocmd VimEnter * :silent! echomsg "silent! echomsg"

When starting vim nothing show up but neither in :messages.

[oblitum]

I don't recall, but the way messages are put gets too much when to dismiss them I get to press Enter, some messages are like this...

[xanderdunn]

I agree with @oblitum that it's way too annoying when I have to press Enter multiple times to get past YouCompleteMe warnings.

If it's not possible to send a message to :messages without bothering the user, or not possible to guarantee that it won't have me press Enter several times, then I'd really love to see an option to completely and utterly disable the YouCompleteMe warnings. I've gotten absolutely no value from them. Yes, they're good for beginners but they're nothing but pain for people who know how to use the plugin.

[Valloric]

While those warnings come with a cost, the benefit they provide is much greater. I'm against adding Yet Another Option to YCM which already has far, far too many. While this option would be a nice-to-have, IMO it's not worth the code complexity and long-term maintenance.

[xanderdunn]

NeoVim to the rescue neovim/neovim#1029.

[oblitum]

That's sad... Personally I would be one of the first to jump into this option. I think options should be weighted on value. This one won't be the default, and would provide much value, given how recurring it's. I guess there may be several other options being provided that don't bring as much value.

[edwinchenloo]

i work with different hosts and with many projects and on some i get warnings everytime i open vim for stuff like vim is an old version or there is no ycm_etra_conf.py file. It is so annoying. I disagree on dismissing a rather useful request because the app already has too many options (which is a personal view). When opening my own .vimrc this plugin also throws error pretty much every time a character in the file changes which is extremely annoying and gets in the way of modifying the file.

Many apps have a debug level of some sort to control log entries like this for a good reason.

[puremourning]

If you're getting an error every time you type a character in a vimrc file, raise a new ticket. We can't help without the data requested in CONTRIBUTING.md.

Importantly, recently there were changes which ensure most (all?) of the warnings don't require you to "Hit enter" or any such.