Ohmster
2005-08-16 06:10:18 UTC
I run fedora core 3 and often use a term program (SecureCRT, it is like
putty.) to ssh to my machine. I have the term program set for VT100 with
ansi color and it works fine. All ls commands are in color, slrn is in
color. vi used to be in color but not anymore. I can run vi (vim,
actually) on the console and I get colors, but if I run vi from my remote
term program, vi is monochrome, not even highlights, just monochrome.
Yet, the term does do color quite nicely.
If I use the screen command from my remote term program and then run vi,
I get my colors back. What could be wrong with vim in that it will no
longer run in color with a vt100 term?
I will output some of my set variables with the "set" command:
TERM=vt100
(no vim color)
Running screen in the terminal:
TERM=screen
(vim color)
When logged into the console locally (No xwindows):
TERM=linux
(vim color)
This vt100 only affects vim. ls and slrn all have good color. Oh, here is
another thing. mc works great on the console and is in good color. mc in
the vt100 remote term window is all monochrome. If I run the screen
command, then mc will run in color in the vt100 term. (I cannot seem to
exit mc with F10 for some reason on the vt100 term, no matter what I do.
I have to just kill the term window to get out of it) So maybe it is not
just a vi issue, but something wrong with the way terms are presented to
certain programs like mc and vim? I really don't know. vi used to work in
color in the vt100 window and now it does not. There is nothing specific
that I can remember changing to make this happen.
Does anyone have any idea as to why vim will not do color anymore in a
vt100 term? I have been at this all night and am cross eyed, I give up,
this is making me nuts. Somebody please take a stab at this. Thanks.
putty.) to ssh to my machine. I have the term program set for VT100 with
ansi color and it works fine. All ls commands are in color, slrn is in
color. vi used to be in color but not anymore. I can run vi (vim,
actually) on the console and I get colors, but if I run vi from my remote
term program, vi is monochrome, not even highlights, just monochrome.
Yet, the term does do color quite nicely.
If I use the screen command from my remote term program and then run vi,
I get my colors back. What could be wrong with vim in that it will no
longer run in color with a vt100 term?
I will output some of my set variables with the "set" command:
TERM=vt100
(no vim color)
Running screen in the terminal:
TERM=screen
(vim color)
When logged into the console locally (No xwindows):
TERM=linux
(vim color)
This vt100 only affects vim. ls and slrn all have good color. Oh, here is
another thing. mc works great on the console and is in good color. mc in
the vt100 remote term window is all monochrome. If I run the screen
command, then mc will run in color in the vt100 term. (I cannot seem to
exit mc with F10 for some reason on the vt100 term, no matter what I do.
I have to just kill the term window to get out of it) So maybe it is not
just a vi issue, but something wrong with the way terms are presented to
certain programs like mc and vim? I really don't know. vi used to work in
color in the vt100 window and now it does not. There is nothing specific
that I can remember changing to make this happen.
Does anyone have any idea as to why vim will not do color anymore in a
vt100 term? I have been at this all night and am cross eyed, I give up,
this is making me nuts. Somebody please take a stab at this. Thanks.
--
~Ohmster
"Read Ohmster" in subject, bypass spam filter.
ohmster /a/t/ newsguy dot com
~Ohmster
"Read Ohmster" in subject, bypass spam filter.
ohmster /a/t/ newsguy dot com