cvs commit: hints xterm-256color.txt

tushar at linuxfromscratch.org tushar at linuxfromscratch.org
Fri Oct 3 22:42:43 PDT 2003


tushar      03/10/03 23:42:43

  Modified:    .        xterm-256color.txt
  Log:
  Updated xterm-256color
  
  Revision  Changes    Path
  1.5       +12 -8     hints/xterm-256color.txt
  
  Index: xterm-256color.txt
  ===================================================================
  RCS file: /home/cvsroot/hints/xterm-256color.txt,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -u -r1.4 -r1.5
  --- xterm-256color.txt	16 Sep 2003 04:54:23 -0000	1.4
  +++ xterm-256color.txt	4 Oct 2003 05:42:43 -0000	1.5
  @@ -1,6 +1,6 @@
   TITLE:		256 color xterm
   
  -DATE:		2003-09-15
  +DATE:		2003-10-03
   
   LFS VERSION:	any
   
  @@ -21,6 +21,10 @@
   to earlier versions of XFree86 4.x.  (Back when there were
   only 3 tarballs for XFree86, xterm was in the first tarball).
   
  +Fri Oct  3 22:09:52 EDT 2003  Reference vim-6.2.  Use 
  +xterm-color as TERM.  Make test programs executable.  Tested
  +with 4.3.99.12.
  +
   
   LICENSE:		GNU Free Documentation License
   
  @@ -56,7 +60,7 @@
   cd xc/programs/xterm &&
   rm -f *.o
   xmkmf &&
  -sed 's/_WIDE_CHARS/_WIDE_CHARS -DOPT_256_COLORS -DDFT_TERM_TYPE=linux/' \
  +sed 's/_WIDE_CHARS/_WIDE_CHARS -DOPT_256_COLORS -DDFT_TERM_TYPE=xterm-color/' \
   	Makefile > Makefile~ &&
   mv Makefile~ Makefile &&
   make &&
  @@ -74,13 +78,12 @@
   make install
   
   5) Update your TERM variable
  -Use linux as your TERM type.  Amazingly it gives better
  -colors than xterm-256color.  You may want
  +Use xterm-color as your TERM type.  You may want
   something like this in your /etc/bashrc:
   
   case `tty` in
   	*/pty*|*/pts/*)	
  -	export TERM=linux
  +	export TERM=xterm-color
   	;;
   esac
   	
  @@ -122,24 +125,25 @@
   8) Log all the way out and come back in.  
   You can do a combination of xrdb and sourcing your .bash_profile,
   but your window manager will still think your TERM is xterm and
  -not linux.  To eliminate confusion, just log out to xdm
  +not xterm-color.  To eliminate confusion, just log out to xdm
   or the login prompt and come back in.
   
   9) Checking colors
   There are several nifty xterm tests in xc/programs/xterm/vttests.  
   The fastest one for testing colors is 256colors2.pl.  Just run:
   
  +chmod +x *.pl
   /256colors2.pl
   
   10) Testing vim colors
   Vim has a colortest program that you run with vim:
   
  -vim /usr/share/vim/vim58/syntax/colortest.vim
  +vim /usr/share/vim/vim62/syntax/colortest.vim
   
   >From inside vim, type:
   :source %
   
  -I counted about 22 colors in this test, but it's nice seeing
  +I counted about 23 colors in this test, but it's nice seeing
   the words associated with the colors.
   
   11) Have fun.  Let me know if something here is inaccurate or
  
  
  



More information about the hints mailing list