On Fri, Apr 22, 2011 at 11:25 PM, Ben Schmidt <[email protected] > wrote:
> The first time I checked the output of the command above for ErrorMsg, >> it showed me the very light colors I had been seeing thus far. I then >> moved cterm=none before ctermbg and ctermfg. This displayed the proper >> colors in the "xxx" area, but now the error window expands, but all >> the text is either not rendering or the same shade of black as my >> terminal background. All I can see is my cursor floating off to the >> right as if it were at the end of a line of text. >> > > Which error window is this? Are you sure that Error and ErrorMsg > highlights are being used in it? > > Are you still referring to errors displayed at startup, i.e. while > loading your .vimrc? It wouldn't surprise me much if colours aren't > fully/properly set up at that stage. Do you get the right colours if you > just use :echoerr or type an invalid command or something? > > Ben. > > > > Normal error's are highlighted fine. Typing :foo shows "Not an editor command: foo" with the proper colors. I'm referring to the error's reported from a syntax error inside my vimrc or other plugin / script. I thought this was the ErrorMsg group's responsibility? What I'm doing to reproduce is the following. - force a typo by changing a "nnoremap" to "nnremap" - :source ~/.vimrc Inside Gvim, the area below my window is expanded and I see this line briefly. E492: Not an editor command nnremap ... etc. Can I change the colors of these types of errors? I experimented with zenburn, and they were in fact highlighted, but I will double check. Thanks -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
