Re: vim syntax highlighting does not work in screen

2006-08-16 Thread aladdin
cga2000 wrote: 1. In vim: .. what is the value of t_Co= ? t_Co=8 by default here. infocmp output shows *colors#8* too, both inside and outside SCREEN. You could try verifying this by issuing a: :set t_Co=8 :set t_Co=16 I tried but makes no difference. .. see if it makes any differen

Re: vim syntax highlighting does not work in screen

2006-08-16 Thread Nikolai Weibull
On 8/16/06, Michael Parson <[EMAIL PROTECTED]> wrote: On Wed, Aug 16, 2006 at 01:54:57PM -0500, Aaron Griffin wrote: > On 8/16/06, Michael Parson <[EMAIL PROTECTED]>wrote: >> On Wed, Aug 16, 2006 at 12:21:17PM -0500, Aaron Griffin wrote: >>> On 8/16/06, aladdin <[EMAIL PROTECTED]>wrote: [EMA

Re: vim syntax highlighting does not work in screen

2006-08-16 Thread Michael Parson
On Wed, Aug 16, 2006 at 01:54:57PM -0500, Aaron Griffin wrote: > On 8/16/06, Michael Parson <[EMAIL PROTECTED]>wrote: >> On Wed, Aug 16, 2006 at 12:21:17PM -0500, Aaron Griffin wrote: >>> On 8/16/06, aladdin <[EMAIL PROTECTED]>wrote: [EMAIL PROTECTED]:~$ set|grep TERM TERM=xterm >>> >>> I

Re: vim syntax highlighting does not work in screen

2006-08-16 Thread Aaron Griffin
On 8/16/06, Michael Parson <[EMAIL PROTECTED]> wrote: On Wed, Aug 16, 2006 at 12:21:17PM -0500, Aaron Griffin wrote: > On 8/16/06, aladdin <[EMAIL PROTECTED]> wrote: >> [EMAIL PROTECTED]:~$ set|grep TERM >> TERM=xterm > > Is this inside screen? screen is a terminal emulator, as is xterm. > The T

Re: vim syntax highlighting does not work in screen

2006-08-16 Thread Michael Parson
On Wed, Aug 16, 2006 at 12:21:17PM -0500, Aaron Griffin wrote: > On 8/16/06, aladdin <[EMAIL PROTECTED]> wrote: >> [EMAIL PROTECTED]:~$ set|grep TERM >> TERM=xterm > > Is this inside screen? screen is a terminal emulator, as is xterm. > The TERM setting should be set to xterm if you're using xter

Re: vim syntax highlighting does not work in screen

2006-08-16 Thread cga2000
On Sun, Aug 13, 2006 at 11:12:19PM EDT, aladdin wrote: > > Hi, all. > > My vim syntax highlighting does not work in SCREEN. > > The problem occurs under RedHat9, vim 6.1.320, SCREEN 4.00.02, remote > login with putty. > > I have another Debian Sarge Linux under which vim and SCREEN work well >

Re: vim syntax highlighting does not work in screen

2006-08-16 Thread Aaron Griffin
On 8/16/06, aladdin <[EMAIL PROTECTED]> wrote: [EMAIL PROTECTED]:~$ set|grep TERM TERM=xterm Is this inside screen? screen is a terminal emulator, as is xterm. The TERM setting should be set to xterm if you're using xterm, and screen if you're using screen. On a side note, TERMCAP is oldschoo

Re: vim syntax highlighting does not work in screen

2006-08-16 Thread Michael Parson
On Wed, Aug 16, 2006 at 11:10:29PM +0800, aladdin wrote: > > Michael Parson wrote: >> >> The vim colorization happens outside of screen? >> >> Do you have "syntax enable" set in your .vimrc? >> > > Sure it works outside of SCREEN. > > Here are some cfg files that may help. Huh. Well, I'm offic

Re: vim syntax highlighting does not work in screen

2006-08-16 Thread aladdin
Michael Parson wrote: The vim colorization happens outside of screen? Do you have "syntax enable" set in your .vimrc? Sure it works outside of SCREEN. Here are some cfg files that may help. * [EMAIL PROTECTED]:~$ cat .vimrc set nocompatible syntax on "highlight Comment cterm

Re: vim syntax highlighting does not work in screen

2006-08-16 Thread Michael Parson
On Wed, Aug 16, 2006 at 03:54:15PM +0800, aladdin wrote: > Thanks for your suggestion. I checked the $TERM env and it was set to > xterm, both inside and outside of SCREEN. But the highlighting and > coloring still did not work. > > BTW, ls --color rendered the output colorized. I configured t

Re: vim syntax highlighting does not work in screen

2006-08-16 Thread aladdin
Michael Parson wrote: What is your TERM env set to? I tend to have mine set to either xterm or vt220, which lets the syntax highlighting and coloring come through. Does color-ls colorizes your ls output? If vim doesn't fire up in colorized mode, I'll usually exit and try it with (under bash)