Date: Thu, 4 Apr 2002 13:21:51 -0500 From: "David S. Jackson" <deepbsd@earthlink.net> To: Kirk Strauser <kirk@strauser.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Default 'TERM' value Message-ID: <20020404132150.L32443@sylvester.dsj.net> In-Reply-To: <87bsd0v875.fsf@pooh.int>; from kirk@strauser.com on Wed, Apr 03, 2002 at 02:27:42PM -0600 References: <87hemszppi.fsf@pooh.int> <20020403134009.B6800@client156-52.ll.siue.edu> <87bsd0v875.fsf@pooh.int>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 03, 2002 at 02:27:42PM -0600 Kirk Strauser <kirk@strauser.com> wrote: > > > xterm*termName: xterm-color > > Upon further searching, I found that I mis-stated the problem. I should > have said "How can I configure *Gnome Terminal* to always set TERM to > xterm-color, to which the answer seems to be "You can't" without use a > command-line argument. :/ TERM variables can be tricky. Sometimes the way to solve the problem is with the problematic application. At first, I set my TERM value to xterm-color and everything was okay as long as I was in X. But when I was at a virtual console, Vim would sometimes show weird characters where colors were supposed to be. The fix eventually seemed to be to change the behavior in my .vimrc: if &term == "xterm" set term=xterm-color else set term=$TERM endif This is just an example of how the fix was not changing TERM and starting a domino chain of events that affected every application that used TERM, but simply changing the behavior of a single application instead. -- David S. Jackson dsj@dsj.net =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I should have been a country-western singer. After all, I'm older than most western countries. -- George Burns To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020404132150.L32443>