Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Add full ANSI color support to UNIX
I was becoming fairly frustrated with because it would not do a good job of displaying ANSI color. I found a hack that would let me display colors with ls, but mutt, lynx, emacs and so on would stubbornly stay in black and white. The solution is to make the proper terminfo file for a VT100 terminal (which is what more or less emulates) with color support.

Read the rest of the article for the how-to...

To do this, grab the files vt100-color.txt and termcap-vt100-color and download them to your home directory. Now, fire up a terminal, and run the following commands (all commands are given in csh syntax since, lamentably, it is the default shell). Make sure you aren't nuking any files you already have there before proceeding:
% mv ~/termcap-vt100-color ~/.termcap
% mkdir ~/.terminfo
% setenv TERMINFO "$HOME/.terminfo"
% tic vt100-color.txt
[Note: In order to run the 'tic' command, you'll need to have 'ncurses' installed and functional. The easiest way to do this is through fink, if you have it installed. Either 'sudo apt-get install ncurses' for the pre-compiled version or 'sudo fink install ncurses' to download and install from source. If you don't have fink installed, you're on your own!]

If everything went right, the command
% ls .terminfo/v
should show a file called vt100-color. The only thing left to do is edit ~/.cshrc and add a line:
setenv TERM vt100-color
You will most likely need to reproduce the above steps (all except for editing .cshrc) for any machine you wish to log into (via, e.g., ssh) and have color capabilities on.

Hope this helps some people! I'll watch the forums if people have feedback/questions.

[Editor's note: I installed this on my machine, and it worked as described.]
  • Currently 2.67 / 5
  You rated: 4 / 5 (6 votes cast)

Add full ANSI color support to | 52 comments | Create New Account
Click here to return to the 'Add full ANSI color support to' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Great Howto, but...
Authored by: afsilva on Apr 09, '02 12:41:11AM

used every command, the envirornment looks good, but all my text still showing up in black... btw, I have been using linux for 7 years, I am not the average mac user ;-)

any other idea why that is happening?


[ Reply to This | # ]
Great Howto, but...
Authored by: acrollet on Apr 09, '02 10:07:01AM

Is color ls what you're looking for? If so, you need the gnu fileutils from fink... (look for /sw/bin/ls)

[ Reply to This | # ]
Authored by: soob on Apr 09, '02 12:45:11AM
I use zsh 4.0.4 and was able to follow the instructions successfully. I have the following function defined in my .zshrc file which allows me to use csh-style setenv to properly set environment variables:
setenv () { export $1=$2 }
and ls .terminfo/v shows a file called vt100-color. I've added
export TERM=vt100-color
to my .zshenv file and made sure new instances have TERM set to vt100-color. Now I just need some way to test. I don't use mutt or lynx and emacs looks the same. Is there some kind of test I can run? I've already got the purdy ls-colors going and midnight commander shows color also, though not as nicely as GLterm. --I must add a caution here... with TERM set to vt100-color, the mouse is no longer able to activate menus in mc using GLterm... commenting out that line brings it back to normal. Thanks, Jim

[ Reply to This | # ]
Authored by: atl on Apr 09, '02 03:13:45AM

so, with this hint, are you sure you can get emacs to do syntax coloring? I had researched this a bit about a year ago, and came away with the impression that it couldn't be done outside of an X display. I would love to be shown to be wrong!

[ Reply to This | # ]
Authored by: acrollet on Apr 09, '02 10:03:33AM

I'm more of a vi kind of guy, but when I logged into a linux box from terminal and ran emacs, I had the proper text colors...

[ Reply to This | # ]
not emacs but xemacs
Authored by: witkamp on Apr 13, '02 12:04:51PM

emacs does not have color syntax in a terminal but xemacs does.
you can get xemacs source and compile it with out a problem. and you will have syntax coloring in terminal mode

[ Reply to This | # ]
Sure emacs can! [was: not emacs but xemacs]
Authored by: on Oct 13, '02 07:54:17AM
This is not true! As of emacs 21 there *are* color support in the terminal! (you just have to know how to enable it...) Put this in your .emacs file ; font-lock, decorate with colours ; Use font-lock in all modes (global-font-lock-mode t) ; And use it with all the whistles (setq font-lock-maximum-decoration t) (set-background-color "Black") (set-foreground-color "White") (set-cursor-color "DarkRed") (custom-set-faces '(font-lock-comment-face ((((class color) (background dark)) (:foreground "Cyan")))) '(font-lock-reference-face ((((class color) (background dark)) (:bold t :foreground "Orange")))) '(font-lock-string-face ((((class color) (background dark)) (:bold t :foreground "Grey")))) '(font-lock-keyword-face ((((class color) (background dark)) (:bold t :foreground "Yellow")))) '(font-lock-warning-face ((((class color) (background dark)) (:bold t :foreground "Red")))) '(font-lock-type-face ((((class color) (background dark)) (:bold t :foreground "Green")))) '(font-lock-variable-name-face ((((class color) (background dark)) (:foreground "Yellow")))) '(font-lock-function-name-face ((((class color) (background dark)) (:bold t :foreground "White"))))) Enjoy!

[ Reply to This | # ]
Authored by: uckoff on Apr 09, '02 05:08:34AM
or do fink install screen then screen or screen mutt screen lynx or screen pine or whatever... full color and keys and everything else works correctly afaict :)

[ Reply to This | # ]
Authored by: acrollet on Apr 09, '02 10:05:09AM

ah, that sounds a lot easier than my solution - I'll have to try that :)

[ Reply to This | # ]
Look in Darwin
Authored by: sabi on Apr 09, '02 09:29:05AM
There are termcap entries in Darwin, referring to terminals called "Apple_Terminal", "Apple_Terminal+acs", "Apple_Terminal+mac", etc.

Here's what I have in my .zshrc so I can get Terminal to be properly recognized elsewhere (I haven't copied the termcap entries everywhere):

if [[ $TERM == "screen" ]] {
} else {
if [[ -z $DISPLAY ]] {
export TERM=vt100
if [[ $TERM == "screen" ]] {
} else {
if [[ -z $DISPLAY ]] {
export TERM=xterm-color

if [[ $TERM == "xterm-color" || $TERM_PROGRAM = "Apple_Terminal" ]] {
prompt="[%U%l:%h%u] %~%#"

chpwd() {
[[ -t 1 ]] || return
if [[ -n $xterm_prompt ]] {
print -Pn "e]2;${USER}@${HOST}:%~a"

[Editor's note: Edited formatting (only!) of code snippet for cleaner display...]

[ Reply to This | # ]
Look in Darwin
Authored by: krokodil on Jan 18, '03 01:05:34AM
Here is how I've expressed it in CSH:
if ( $TERM_PROGRAM == Apple_Terminal) then
        setenv TERM vt100-color

[ Reply to This | # ]
To .cshrc or .tcshrc?
Authored by: digitalee on Apr 09, '02 06:27:06PM

I was eventually able to get a recognition of the tweak (everything in your instructions responded as stated) but no noticeable difference yet in emacs or lynx.

I'm a little confused...I've seen references in the past to setting up a .csrhc & other times a .tcshrc. Is one an MOSX standard and will either/or both suffice?

Thanks for the tip!

[ Reply to This | # ]
I may have got it...but not as root user?
Authored by: digitalee on Apr 09, '02 06:47:27PM

Incidently, when I try this for the root user I get the following error message:

emacs: Terminal type vt100-color is not defined.
If that is not the actual type of terminal you have,
use the Bourne shell command `TERM=... export TERM' (C-shell:
`setenv TERM ...') to specify the correct type. It may be necessary
to do `unset TERMCAP' (C-shell: `unsetenv TERMCAP') as well.

I followed the same procedure as for my regular login, all while sudoed into root, except put the files in /private/var/root ...

Am I missing something here?

Thanks much.

[ Reply to This | # ]
To .cshrc or .tcshrc?
Authored by: atl on Apr 11, '02 07:12:35PM
if it's the "MOSX standard" that you're looking for, take a look at /usr/share/init/tcsh/README... That's how the default shell is set up to work: do your customizations in ~/Library/init/tcsh/.

[ Reply to This | # ]
Problems with ls ls .terminfo/v
Authored by: ricosuave on Apr 09, '02 07:48:50PM

I have tried to follow your directions to the letter, but have come across a problem. When i try to enter
% ls .terminfo/v
I get an error :
ls: .terminfo/v: No such file or directory
I checked the permissions of the directory and they are fine, the directory exists as I can see it with ls -la but it won't give me the result shown in the original directions for full ansi color.
I can do ls .terminfo but it does not give me vt100-color as stated. Any hints or suggestions?

[ Reply to This | # ]
Problems with ls ls .terminfo/v
Authored by: WillyT on Apr 09, '02 09:48:30PM

Did you by chance (like I did) accidently type TERMCAP instead of TERMINFO in the setenv command. If so unsetenv TERMCAP should fix it then do the tic again. Also be sure to DL the files. Don't cut and paste to an editor as you will get carriage returns instead of line feeds.

[ Reply to This | # ]
More Problems...
Authored by: Telluride on Apr 09, '02 11:19:44PM

Ok, i followed the instructions exactly, but alas still no colors. Perhaps its because i have the translucency effect enabled?? I have the ~/.terminfo/v dir with vt100-color in it, i have the .termcap file, i followed the command instructions for setenv ..." and tic (i have ncurses!)...everything looks fine, but i cannot get colors with ls, or lynx, or emacs....woe is me! Any help would be greatly appreciated

[ Reply to This | # ]
Still Problems...
Authored by: WillyT on Apr 10, '02 10:04:51AM

Well I've got color but I had color before with the lc command. But All the ANSI stuff still seems to be broken. An old ansi file of Bart S. displays fine in xterm but is still garbage in the terminal.. Still NO ansi escapes from the command line. Cut(oh boy) and Paste(!DANGER Will Robinson!) work to the terminal(with NO CR/LF translation). .Apple Terminal still sucks except for transparency. So what if any of this is the hint supposed to fix. or is the terminal broken beyond repair.
Sorry But I'm NOT critizing the hint or author just (And I'm still Grumpy with the time change)

[ Reply to This | # ]
More Problems...
Authored by: jonasbn on Oct 27, '02 07:25:02AM

I actually solved a similar problem in a very simple way.

Some terminal apps do not recognise the vt100-color terminal type, and therefor refuse to run.

Change the name of the terminal specified in the two files you are asked to download from vt100-color to vt100, which actually mean that you 'cheat' the terminal into believe it is a vt100, and it is but with colors.

So now pine, vim and everything else works (haven't tried emacs)...

[ Reply to This | # ]
ncurses didn't install properly
Authored by: macubergeek on Apr 10, '02 01:13:36PM

I got weird make errors when installing ncurses from source. I downloaded source from gnu page so I'm figuring I have to do configure with special flags. Will retry to install ncurses tonight when I have the time.

[ Reply to This | # ]
Doesn't work for me...
Authored by: AndreasG on Apr 10, '02 06:54:09PM


I did everything as described in the hint -- with no noticeable difference... Are there any hidden traps? (When I executed the commands everything seemed to work OK...)

Thanks for any help, Andreas

[ Reply to This | # ]
Doesn't work for me...
Authored by: AndreasG on Apr 10, '02 08:24:45PM

...oh just discovered: Colors _do_ work when I use Gnome's Terminal, but the do _not_ work in or regular xterm.... What does that mean?

[ Reply to This | # ]
ncurses wont install
Authored by: macubergeek on Apr 10, '02 08:23:24PM

Ok I regret not installing ncurses via fink
Ncurses is evil...just plain evil

I did
./configure -host=powerpc-apple-macosx

make kicked up a myriad of byzantine, cryptic errors scrolling by too fast to recall.

I did sudo make install and after yet more cryptic gibberish flying by too fast to read...I'm left with this make error:
"/tmp/17163", line 395, col 3, terminal 'ecma+color': unknown capability 'AX'
"/tmp/17163", line 3193, col 40, terminal 'screen': unknown capability 'G0'
"/tmp/17163", line 3212, col 59, terminal 'screen': unknown capability 'E0'
"/tmp/17163", line 3213, col 12, terminal 'screen': unknown capability 'S0'
"/tmp/17163", line 3165, terminal 'eterm': name multiply defined.
"/tmp/17163", line 12958, terminal 'NCR260VT300WPP': can't link N/NCR260VT300WPP to n/ncr260vt300wpp
? tic could not build /usr/local/share/terminfo
make[1]: *** [] Error 1
make: *** [install] Error 2
jamesk @ /Users/jamesk/Desktop/ncurses-5.2@HOME-->

does anyone have any ideas on how to fix this?
When I try to install ncurses via fink after this it tells me ncurses is installed. How do I test to see if it installed. Geeeeze unix programs are such barfy whiny complaining beasties ;-(

[ Reply to This | # ]
ncurses wont install
Authored by: dlandrith on May 08, '02 07:59:13PM

You need to apply a patch to the source that has been available for (about 9 months). The gnu ftp site (and its mirrors) do not have any of the patches online, so you have to go straight to the home ftp site for ncurses. Following is the address to the patch directory on Thomas Dickey's ftp server:

The simplest way to apply the patch is to grab the lastest "rollup" patch that the author (Thomas Dickey) has made. Once a month, he takes all of the latest patches and creates a shell script that will update the source. The way that you do this is to untar and gunzip the ncurses download, gnunzip the patch, then copy the patch to the ncurses directory (the one that resulted from untaring and gunziping it), then running it by typing sh <patch name>.

Then do configure --prefix=/usr/local --mandir=/usr/local/share/man; make; make install.

It will compile and install without a hitch.

You really should have ncurses installed for whenever you compile a terminal program. BSD curses (the standard libcurses and curses.h) are really very buggy, especially if you are doing programming. Moreover, ncurses does quite a bit more and almost every terminal based program will take advantage of it.

[ Reply to This | # ]
Authored by: macubergeek on Apr 10, '02 09:31:41PM

ncurses (the evil one) DID install and I know this because I installed an ncurses application via fink and it works fine. colors. none. I guess I'll have to settle for half a loaf.

[ Reply to This | # ]
Authored by: Vlad on Apr 11, '02 02:59:08PM

Try something like this:
ls --color=yes

If that will help, then add an alias (I use tcsh):
alias ls "ls --color=yes"


[ Reply to This | # ]
Doesn't work for me too!
Authored by: tuang on Apr 23, '02 02:32:28PM

I've done everthing as the hint said.
Everything work smoothly, but still nothing happen.
Does it has something to do with preference, coz the only
color I see now is a color I've set in that perference.
can anybody show some those working screens shot?
thanks a lot.

[ Reply to This | # ]
works, but annoying when ssh
Authored by: the_shrubber on May 09, '02 12:11:49PM

it gets very annoying if you use ssh a lot, because the other end thinks that you're in vt100-color, which it doesn't recognise. I suppose i *could* alias ssh to reset to vt100 and back, but is there a better solution?

[ Reply to This | # ]
works, but annoying when ssh
Authored by: serversurfer on Jun 14, '02 09:01:12AM
Try adding this to ~/Library/inti/tcsh/rc.mine
# Check to see if we are being run via remote-login and set TERM accordingly.
if ( $?SSH_CLIENT ) then
set TERM = "vt100"
set TERM = "vt100-color"

[ Reply to This | # ]
vi 6, lynx and it works
Authored by: philoew on May 19, '02 10:07:23PM

Thank you, this worked for me, I updated my version of vim and lost my syntax color highlighting but this tip fixed my problems and now I have color in lynx and other programs. Thanks again.

[ Reply to This | # ]
SSH solution
Authored by: melo on Jun 13, '02 11:16:00AM

Thanks for this tip. Not only does it work for Terminal but also for xterm..

Regarding the SSH problem (exporting to the remote host the TERM=vt100-color), my solution was this (bash syntax, adapt to your favorit shell):

alias ssh="TERM=vt100 ssh"

Best regards

[ Reply to This | # ]
SSH solution for tcsh?
Authored by: soulrider2k on Nov 05, '02 09:49:30PM

"alias ssh 'set TERM=vt100 ;ssh'"
to .tcshrc (I don't use bash :-)

any idas why i get:
[habanero:~] bryan% ssh
Alias loop.
[habanero:~] bryan%

back when attempting ssh connections?

I don't appear to have any other ssh aliases...

[habanero:~] bryan% alias | grep ssh
ahost clear; ssh admin@hostx
ct clear; ssh host1
g2k clear; ssh boys@host2
pps clear; ssh admin@host3
skully clear; ssh bryan@host4
ssh set TERM=vt100 ;ssh

Any thoughts would be most welcome. I am STOKED that I found this thread, I am so sick of invoking screen when i want to edit a file with vim (:syntax on)

[ Reply to This | # ]
SSH solution for tcsh?
Authored by: melo on Nov 06, '02 08:15:11AM

The alias you use end's with ssh again, so tcsh tries to replace it again... It creates a alias loop.

Try this:

alias ssh 'set TERM=vt100; /usr/bin/ssh'

Best regards,

[ Reply to This | # ]
SSH solution for tcsh?
Authored by: soulrider2k on Nov 06, '02 07:36:30PM

I found a solution for this.
when using tcsh, put this in your .tcshrc file.....

alias ssh 'setenv TERM vt100;/usr/bin/ssh'


[ Reply to This | # ]
How to add alternate box charset to vt100-color
Authored by: carsten on Aug 28, '02 07:37:47PM

Some curses programs can draw nice boxes using an alternate character set, instead of using ascii characters like hyphens, pluses and pipes. (giFTcurs is one such program, it's available in the fink unstable tree at the time of this writing).

After a lot of research and trial and error I finally figured out how to enable the alt charset mode. Finally I copied these lines from the vt100 term info file (infocmp -L -1 vt100) and it works!

Add the following lines to the vt100-color.txt file before you run tic: acs_chars=``aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~, ena_acs=E(BE)0, enter_alt_charset_mode=^N, enter_am_mode=E[?7h, enter_blink_mode=E[5m$, exit_alt_charset_mode=^O, exit_am_mode=E[?7l,

or replace all the contents of the vt100-color.txt file with these lines (there are also a few other keymapping lines added here found in vt100 which are not in the vt100-color.txt file supplied above): vt100-color|vt100-colour|VT100 with ANSI colour support, auto_right_margin, eat_newline_glitch, columns#80, init_tabs#8, lines#24, max_colors#8, max_pairs#64, virtual_terminal#3, acs_chars=``aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~, bell=^G, carriage_return=^M, change_scroll_region=E[%i%p1%d;%p2%dr, clear_screen=E[;HE[2J, clr_eol=E[K$, clr_eos=E[J$, cursor_address=E[%i%p1%d;%p2%dH$, cursor_down=^J, cursor_home=E[H, cursor_left=^H, cursor_right=E[C$, cursor_up=E[A$, ena_acs=E(BE)0, enter_alt_charset_mode=^N, enter_am_mode=E[?7h, enter_blink_mode=E[5m$, enter_bold_mode=E[1m$, enter_reverse_mode=E[7m$, enter_standout_mode=E[7m$, enter_underline_mode=E[4m$, exit_alt_charset_mode=^O, exit_am_mode=E[?7l, exit_attribute_mode=E[m$, exit_standout_mode=E[m$, exit_underline_mode=E[m$, key_a1=EOq, key_a3=EOs, key_b2=EOr, key_backspace=^H, key_c1=EOp, key_c3=EOn, key_down=EOB, key_enter=EOM, key_f0=EOy, key_f1=EOP, key_f10=EOx, key_f2=EOQ, key_f3=EOR, key_f4=EOS, key_f5=EOt, key_f6=EOu, key_f7=EOv, key_f8=EOl, key_f9=EOw, key_left=EOD, key_right=EOC, key_up=EOA, keypad_local=E[?1lE>, keypad_xmit=E[?1hE=, newline=rED$, orig_pair=E[m, reset_2string=E>E[?3lE[?4lE[?5lE[?7hE[?8hE[;rE[0mE(BE)BE[2J, reset_file=/usr/share/tabset/vt100, restore_cursor=E8, save_cursor=E7, scroll_forward=ED$, scroll_reverse=EM$, set_a_background=E[4%p1%dm, set_a_foreground=E[3%p1%dm, set_background=E[4%p1%dm, set_foreground=E[3%p1%dm, tab=^I, references: (not for the queasy)

[ Reply to This | # ]
ANSI Color support in
Authored by: marleyg on Aug 29, '02 05:23:49PM

I am curious to know if you have used your patch with Jaguar?
Also, do you know what would be required to configure SCO-ANSI 16 color emulation?

[ Reply to This | # ]
ANSI Color support in
Authored by: carsten on Aug 29, '02 06:33:38PM

Actually I have only tested the alternate box char patch in Jaguar, but it should work in 10.1.5 as well.

16 color support would be nice too, I'm going to see how that might be done.

Also I think there may be a problem with UTF-8 in Jaguar's terminal, characters like ΓΌ show up as u?? in directory listings even without any vt100-color term files installed. Can anyone else confirm this?

[ Reply to This | # ]
TERMINFO, et al fixed under 10.2 Jaguar
Authored by: thaislump on Sep 17, '02 04:45:47PM

I wanted to say that it seems the whole TERMINFO/TERMCAP problem seems to have been resolved by Apple with the release of 10.2 Jaguar. For instance, the old termcap file in /usr/share/misc is no longer there, indicating they moved to a TERMINFO database. In fact, using vim from the command-line yields the expected colors with syntax mode enabled.

[ Reply to This | # ]
ANSI and Color
Authored by: area51 on Oct 18, '02 03:46:01AM

Is it possible to have more than 16 colors in vim? I had to set the TERM env variable to ansi for any colors to show up in vim but I seem to be limited to 16. I'm running 10.2.1 and using the Apple Terminal program.

[ Reply to This | # ]
tcsh ssh alias working!
Authored by: soulrider2k on Nov 06, '02 03:06:18PM

I got it late last night...

in your .tcshrc (for tcsh users)

alias ssh 'setenv TERM vt100;/usr/bin/ssh'


[ Reply to This | # ]
some problems
Authored by: DMCrimson on Nov 20, '02 02:03:53PM

I did this and now everytime I open terminal, it gives me error 'name collision vt100 vt100' and same when running pico/nano or whatever...but they work...any ideas?

[ Reply to This | # ]
Great Hint But...
Authored by: DoctorPepper on Dec 05, '02 07:45:45PM

I ran into the same problem with ssh that some other poster's did. my solution to this problem was to delete all the newly created termcap info. I then renamed the vt100-color.txt file to "vt100.txt" and changed the "vt100-color:\" line in the termcap-vt100-color file to "vt100:\". I proceded with the rest of the setup, except where ever the directions called for "vt100-color", I simply entered "vt100". It works like a charm. I have color in my OS X terminal AND color in my ssh sessions, without having to resort to alias'.

[ Reply to This | # ]
tic doesn't output anything
Authored by: chrislyon on Dec 10, '02 06:47:08PM

I 've followed the instructions carrefully. Fink is installed and I've updated the package ncurses. But tic doesn't compile the vt100-color.text into binary. When I put -V option to force tic verbosing, it writes only "ncurses 5.2.20001021". Does someone know about that problem ? Or is it possible to find compiled version of vt100-color ?

Thank you in advance

[ Reply to This | # ]
Use "dtterm"
Authored by: uucee on Jan 19, '03 07:57:36AM
Set TERM to "dtterm". Try even running some of the vttest dtterm-specific tests on You'll be surprised. emacs and lynx seem to work w/o problems in color.

[ Reply to This | # ]
Use "dtterm"
Authored by: soulrider2k on Jun 20, '03 01:22:41AM

this is the simplest most kickass soulution. Put:

setenv TERM dtterm

into your .tcshrc file


[ Reply to This | # ]
Use "nsterm"
Authored by: GaelicWizard on Jul 10, '03 12:46:14AM

nsterm or Apple_Terminal
This is what the terminal actually is. No tricks, no fixes, no hacks, no cracks. This is it. Apple just didn't set it to this... why?


[ Reply to This | # ]
Add full ANSI color support to
Authored by: grammyputer on Sep 26, '03 03:52:53PM

Looks like exactly what I was looking for, but the links to the text files are dead.

[ Reply to This | # ]
Add full ANSI color support to
Authored by: nentis on Oct 15, '03 08:51:51PM

I use bash, and added the following to my ~/.bash_profile

export TERM=xterm-color

ls and mutt work just fine.

[ Reply to This | # ]
Add full ANSI color support to
Authored by: DMCrimson on Dec 23, '03 08:40:11AM

got this to work... but for some reason the tic'd file went to .terminfo/76/ rather than .terminfo/v/ as was supposed to... mv saves:) oh, the files are gone from original links, but wayback machine found them.

[ Reply to This | # ]
Add full ANSI color support to
Authored by: Cerberus on Apr 11, '04 12:32:59AM

I am on 10.3.3 and checking MAN LS shows this:

-G Enable colorized output. This option is equivalent to defining
CLICOLOR in the environment. (See below.)

MANPAGE is date May 19, 2002

So I setup my alias as ls="ls -G" and colors, colors, colors everywhere... Hopefully this will save a few from having to venture too far from the CLI ;-)

[ Reply to This | # ]
Add full ANSI color support to
Authored by: chienr on May 05, '04 10:14:04PM

If this hint doesn't work for you, or you find it too cumbersome, you can try:

if using bash: export TERM=dtterm
if using csh/tcsh: setenv TERM dtterm

[ Reply to This | # ]
Add full ANSI color support to
Authored by: Eljay on Mar 24, '07 04:18:35AM

This worked for me, using NCurses (5.4) or Vim (7.0p51) or Angband or other terminfo savvy applications (OS X 10.4.9, v1.5 (133)), in my ~/.bashrc:

export TERM=xterm-16color

It worked far better than TERM=Apple_Terminal or TERM=xterm-color.

Take a look at the infocmp -1afE dump of xterm-16color versus Apple_Terminal or xterm-color and you'll see why. Looks like Apple_Terminal terminfo has not been kept up to date with Tsk tsk.

[ Reply to This | # ]