Sunday, November 3, 2013

't_Co' is always set to 256 if 'nocompatible' is set

Since I updated to Vim 7.4 I'm seeing this strange behaviour:

$ echo $TERM
xterm-16color
$ vim
:set t_Co?
t_Co=256

I first suspected that something is wrong with my vimrc, but starting without
a vimrc behaves the same:

$ vim -Nu NONE
:set t_Co?
t_Co=256

What's really wierd is, that if I start Vim without 'nocompatible' then 't_Co'
is set to the correct value:

$ vim -u NONE
:set t_Co?
t_Co=16

This was definitely *not* happening with older versions of Vim. Now, is this
a bug or somehow intended? Can anybody reproduce this?

Thanks,
Dustin

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