Post #171,059
8/26/04 1:05:09 PM
|
Any idea why vim 6.3 doesn't know I've got a color terminal?
A recent apt-get upgrade took me from vim 6.2 to vim 6.3. Now it doesn't use color any more. I seem to remember having this problem before and fixing it, so it could be that I lost a modified config file somewhere. What should I be looking for?
While working on this I realized I shouldn't have done something I did a while back. I knew there were configs I always wanted in vim, so I modified the global vimrc instead of installing a personal .vimrc. Now every time there's an update apt asks me if I want to keep my locally-modified vimrc or take the maintainer's version. Is there a way to pull just the vimrc file from the package and install that?
===
Implicitly condoning stupidity since 2001.
|
Post #171,063
8/26/04 2:42:51 PM
|
Yes.
Remember that thing about implicitly condoning stupidity? but first we gotta know what gvim you have: Package gvim is a virtual package provided by:\n vim-tcl 1:6.3-015+1\n vim-ruby 1:6.3-015+1\n vim-python 1:6.3-015+1\n vim-perl 1:6.3-015+1\n vim-lesstif 1:6.3-015+1\n vim-gtk 1:6.3-015+1\n vim-gnome 1:6.3-015+1 Uh, which one. But anyway, the process is the same: mkdir foo ; cd foo
dpkg-deb -x /where/the/packge/is/virt-gvim-someversion.i386.deb .That will extract the package with foo/ as the "rootdir" get the file(s) you want out of there. BTW gvim is prolly vim with the "named version" added to it. -- [link|mailto:greg@gregfolkert.net|greg], [link|http://www.iwethey.org/ed_curry|REMEMBER ED CURRY!] @ iwetheyNo matter how much Microsoft supporters whine about how Linux and other operating systems have just as many bugs as their operating systems do, the bottom line is that the serious, gut-wrenching problems happen on Windows, not on Linux, not on Mac OS. -- [link|http://www.eweek.com/article2/0,1759,1622086,00.asp|source]Here is an example: [link|http://www.greymagic.com/security/advisories/gm001-ie/|Executing arbitrary commands without Active Scripting or ActiveX when using Windows]
|
Post #171,078
8/26/04 3:27:30 PM
|
Not gvim ... vim
dkime-linux:~$ dpkg -l | grep vim
ii vim 6.3-015+1 Vi IMproved - enhanced vi editor
ii vim-common 6.3-015+1 Vi IMproved - Common files
===
Implicitly condoning stupidity since 2001.
|
Post #171,142
8/26/04 9:37:51 PM
|
Two things.
Does the 6.3 vim global file turn on syntax highlighting or not? If 6.2 does, or you added that, and 6.3 doesn't it would look like it's forgotten you have a colour terminal.
The other thing is that the rules might have changed slightly for telling the syntax highlighting that you can do colour based on your TERM setting. I remember having that problem within screen somewhere when my TERM when slightly funny after an SSH.
Wade.
Is it enough to love
Is it enough to breathe
Somebody rip my heart out
And leave me here to bleed
| |
Is it enough to die
Somebody save my life
I'd rather be Anything but Ordinary
Please
| -- "Anything but Ordinary" by Avril Lavigne. |
|
Post #171,365
8/27/04 5:11:48 PM
|
Yes, syntax is on in the new vimrc
===
Implicitly condoning stupidity since 2001.
|
Post #171,245
8/27/04 12:29:05 PM
|
ln -sf /usr/bin/emacs /usr/bin/vim
Problem solved :-)
Otherwise, it's over to Greg at the sports desk.
Peter
[link|http://www.debian.org|Shill For Hire]
[link|http://www.kuro5hin.org|There is no K5 Cabal]
[link|http://guildenstern.dyndns.org|Blog]
|
Post #175,595
9/22/04 5:26:44 AM
|
Re: Any idea why vim 6.3 doesn't know I've got a color termi
in /etc/vim/vimrc, search the path, and change vim62 to vim63.
nnn
|
Post #175,611
9/22/04 9:00:01 AM
|
Cool, that seems to be *half* the problem
It's no longer complaining that it can't find the colorscheme. But it's still monochrome. :-/
===
Implicitly condoning stupidity since 2001.
|
Post #175,609
9/22/04 8:56:45 AM
|
:syntax on OSLT, put in .vimrc
-drl
|
Post #175,612
9/22/04 9:02:04 AM
|
It's there, syntax *is* being hilighted
It's just being hilighted as bold or reverse. No colors.
===
Implicitly condoning stupidity since 2001.
|
Post #175,682
9/22/04 12:07:50 PM
|
Then check $TERM
Sounds like vt100 disease.
-drl
|
Post #175,721
9/22/04 1:22:29 PM
|
$TERM is Eterm
I vaguely remember having to deal with this when I switched to eterm. Now to dig through configs and see where it identifies that ...
===
Implicitly condoning stupidity since 2001.
|
Post #175,760
9/22/04 2:34:51 PM
|
Are you using E-Term?
Or are you using Gnome Terminal?
-- [link|mailto:greg@gregfolkert.net|greg], [link|http://www.iwethey.org/ed_curry|REMEMBER ED CURRY!] @ iwetheyNo matter how much Microsoft supporters whine about how Linux and other operating systems have just as many bugs as their operating systems do, the bottom line is that the serious, gut-wrenching problems happen on Windows, not on Linux, not on Mac OS. -- [link|http://www.eweek.com/article2/0,1759,1622086,00.asp|source]Here is an example: [link|http://www.greymagic.com/security/advisories/gm001-ie/|Executing arbitrary commands without Active Scripting or ActiveX when using Windows]
|
Post #175,767
9/22/04 2:45:15 PM
9/22/04 2:45:58 PM
|
Yes, E-Term
And I have been for a while. Colors worked with vim6.2, stopped when I got vim6.3.
===
Implicitly condoning stupidity since 2001.
Edited by drewk
Sept. 22, 2004, 02:45:58 PM EDT
|
Post #175,779
9/22/04 3:27:02 PM
|
I believe that...
E-Term used to use another $TERM spec until recently.
This might have been the whole cause inconjunction with the 6.2->6.3 issue.
Force E-Term to use an xterm definition.
TERM=xterm
to check to see if that *IS* the issue :
export TERM=xterm
If that fixes it, you now know where you problem exists.
-- [link|mailto:greg@gregfolkert.net|greg], [link|http://www.iwethey.org/ed_curry|REMEMBER ED CURRY!] @ iwetheyNo matter how much Microsoft supporters whine about how Linux and other operating systems have just as many bugs as their operating systems do, the bottom line is that the serious, gut-wrenching problems happen on Windows, not on Linux, not on Mac OS. -- [link|http://www.eweek.com/article2/0,1759,1622086,00.asp|source]Here is an example: [link|http://www.greymagic.com/security/advisories/gm001-ie/|Executing arbitrary commands without Active Scripting or ActiveX when using Windows]
|
Post #175,787
9/22/04 3:58:43 PM
|
Tried it
Tried TERM-xterm, xterm-color, linux, etc etc etc. No joy.
===
Implicitly condoning stupidity since 2001.
|
