charlesgueunet / vimmic Goto Github PK

I updated vimmic today since then neovim start with the following error message:

Error detected while processing VimEnter Autocommands for "*":
E418: Illegal value: red

Starting neovim in debug mode results in the following:

autocommand highlight ALEVirtualTextError cterm=red cterm=bold
Press ENTER or type command to continue
Error detected while processing VimEnter Autocommands for "":
E418: Illegal value: red
Press ENTER or type command to continue
autocommand highlight ALEVirtualTextWarning cterm=yellow cterm=bold
Press ENTER or type command to continue
Error detected while processing VimEnter Autocommands for "":
E418: Illegal value: yellow
Press ENTER or type command to continue
autocommand highlight ALEVirtualTextIngo cterm=cyan cterm=bold
Press ENTER or type command to continue
Error detected while processing VimEnter Autocommands for "*":
E418: Illegal value: cyan

Searching in .vimmic it seems to be the lines 22 - 26 in the config file Ale.vim is the issue.

According to the Nvim documentation allowed values for cterm are "bold" and "underline". For colors ctermfg and/or ctermbg has to be used.

Vimmic is configured to automatically open a popup window once he can (instead of using, for example, <C-P>)

" automatically open and close the popup menu / preview window
au CursorMovedI,InsertLeave * if pumvisible() == 0|silent! pclose|endif

However this configuration is mixed with the following one:

inoremap <expr> j ((pumvisible())?("\<C-n>"):("j"))
inoremap <expr> k ((pumvisible())?("\<C-p>"):("k")) 

Which allows the user to navigate with keys j and k in the popup window in insert mode.

This feature is interesting, but can be harmful in some cases. For example considere the following snippet:

const LOCK_SOMETHING = true

func MyFunc() {
    mystring := "I am using a loc|      <----- Vim cursor is here

A popen opens, which will suggest LOCK_SOMETHING while writing loc. By pressing k, I enter in the popup and choose the first occurence (i.e. LOCK_SOMETHING) which was not intended.

This behaviour might be harmful for vim begginers (like me!). My suggestion would be to put in the documentation the two inoremap lines and disable them by default.