Tuesday, December 10, 2013

Re: Colors when opening a file where a swap file exists

On Tuesday, December 10, 2013 10:59:52 AM UTC+1, Christian Brabandt wrote:
> Sorry, I think, I meant the MoreMsg highlighting group. There is no
> ConfirmMsg highlighting group.
>
> What I mean is, if you see this message when starting vim or gvim,
> then by that time, Vim hasn't adjusted the colors to the corresponding
> colorscheme yet, simply because is hasn't sourced your colorscheme
> yet, so it uses a compiled default, which might not match your
> terminal. You can tell by provoking this message again, after Vim was
> loaded, and see, if Vim uses a different color then.

Yes, that seem to be the case. If I open another file which is already open after I've opened the first the message is in the color that I've set.

> What should work however is to reset the 'hl' setting by e.g.
> vim --cmd "let &hl=substitute(&hl, 'm:[^,]*,', 'm:ErrorMsg,', '')"
> foobar

I tried this and then the message was shown with the color that ErrorMsg has.

> But it might be easier to configure your terminal correctly. What
> terminal are you using and what is your $TERM variable? It might
> already help to force Vim to use a 't_Co' setting of 256, e.g. do an
> export TERM=xterm-256colors
> in your terminal (or whathever your shell needs)

I'm using iTerm2 and TERM is set to xterm-256color. If I run :set t_Co? inside vim I get 256.

--
--
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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment