On Fri, Apr 03, 2009 at 06:09:43AM +0200, Tony Mechelynck wrote: > > On 03/04/09 05:47, Taylor Venable wrote: > > On Thu, Apr 02, 2009 at 07:51:21PM -0700, Gary Johnson wrote: > [...] > >> > >> :verbose set t_Co? > > > > Somebody on IRC suggested this too but all this command shows is that > > t_Co = 256 and no hint of where it came from. The value is definitely > > 8 while .vimrc is being executed but at some point after that (also > > after the VimEnter autocommand) it's being set to 256. > > > > Is 'term' (not $TERM) set to the same value while sourcing the vimrc and > after VimEnter? ":verbose set term?" will tell you its value, and if any > script changed it.
Same behaviour (all I see is the value, there is no history of changes). Also, by putting 'echo &term' into my .vimrc I see that it is xterm-color all the way through until Vim has loaded, then I can type ':set term' and see that it is still xterm-color. -- Taylor Christopher Venable http://real.metasyntax.net:2357/ foldr = lambda f, i, l: (len(l) == 1 and [f(l[0], i)] or [f(l[0], foldr(f, i, l[1:]))])[0] --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
