On 2011-04-23, Tony Mechelynck wrote:
> On 23/04/11 04:26, Alan Warren wrote:
> >:verbose hi Error
> >Error xxx term=reverse ctermfg=128 ctermbg=234 guifg=#af00d7
> >guibg=#191919
> > Last set from ~/.vim/colors/eclm_special_256.vim
> >
> >:verbose hi ErrorMsg
> >ErrorMsg xxx term=standout ctermfg=128 ctermbg=234 guifg=#af00d7
> >guibg=#191919
> > Last set from ~/.vim/colors/eclm_special_256.vim
> >
> >
> >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.
> >
> >I tested using Gvim, and the error is visible, but remains white on red.
> >
> >Could the term=standout have something to do with this?
>
> No. The term= argument is (or rather, was) only used on monochrome
> terminals such as those fed by video cards like the IBM-PC MDA or the
> Hercules HGC. On color text or graphics cards it is totally ignored.
The term argument is still used if terminfo reports that your
terminal is monochrome, i.e., does not report a value for t_Co.
If you're using xterm or an xterm-like terminal, you can see the
effect of various term= arguments if you start vim as
$ TERM=xterm-old vim
then execute
:hi
and
:runtime syntax/hitest.vim
Regards,
Gary
--
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
