VT100 ANSI Terminal Color

[AndreasG]

Hi,

I followed the instructions of a hint "enabling ANSI colors for Terminal.app", which was posted in the UNIX section a few days ago. It didn't work for me (in fact I didn't notice any difference...), although everything seemed to go the right way (I got the right "ls" output as mentioned in the hint).

1. I would like to actually _understand_ what I am doing here -- can anybody explain this or post links where I can read about VT100, ANSI Color etc. I really like to read first and ask for help afterwards -- I just don't know where to start...
The contents of the .termcap file look quite intimidating to a not-so-experienced UNIX user like me and until now I don't even know what VT100 means... sorry...

2. Can anybody make a guess why this didn't work for me? I really would be happy to have more color in Terminal.app, especially for programs like mc (mc actually has color when run from a Gnome terminal but not from xterm or Terminal.app).

I appreciate your help very much.

Thanks, Andreas

P.S.: Hardware: TiBook500, OS X 10.1.3, I used fink to install GNU fileutils, GNOME, Gimp and many more..., "ls" from fileutils displays color correctly.

[jmeador]

For VT100 terminal info, check out


http://www.cs.utk.edu/~shuford/terminal_index.html

http://vt100.net/

and their faq http://vt100.net/terminals_faq

[sao]

AndreasG,

Which hint did you followed ?

Anyhow, here is a link to the ANSI/VT100 Terminal Control Escape Sequences:

http://www.termsys.demon.co.uk/vtansi.htm

Have you changed your prompt colors?

If you didn't, let me know, is very easy to do it.



Cheers...

[AndreasG]

Hi sao,

thanks for your reply. The hint in question is this one:

http://www.macosxhints.com/article.p...20408225741777

"Add full ANSI color support to Terminal.app", posted Mon, Apr 8 '02 at 10:57PM • from: acrollet

Cheers, Andreas

P.S.: I didn't change my prompt colors -- actually what I wanted to do is to enable certain applications like mc, emacs and pine to display color.

[sao]

AndreasG,

Long ago, I posted a link to a similar tip in the 'Terminal Mods' thread at Unix Beginners :

http://forums.macosxhints.com/showth...=&threadid=421

If you're really interested, maybe you can try to follow this one. It's not so easy, though. And please, backup your files first.

http://www.kung-foo.tv/termcap.html

Another thing you could do, is to install 'screen' with fink.


Cheers...

[AndreasG]

I have screen installed via fink! But it doesn't give me color....

[WillyT]

Hi sao

I am grumpy because I can't get Esc [32m to work in the terminal or xterm. Is the CSI disabled by the hardware. G4 400Mhz Sawtooth.
1) The Esc does not print -- good
2) The bracket does not print -- good
3) The 3 does not print but gives a warning bell -- not so good
4) The 2 prints -- failure

Does this work for you?

Also other than from the keyboard ANSI works in xterm but not in the terminal. I get the color in the terminal but none of the positional stuff seems to work.

P.S. I tried the hint but it didnt fix what I wanted.

Willy

[sao]

AndreasG,

I read your posts at fink-users.

Have you tried the tip from Chris Zubrzycki :

<<I found something that works, at least on mac systems. Make sure you have ncurses installed, and put this in your .bashrc:

# Fix the term variable in OS X

if [ "$TERM" == "network" ]; then
export TERM=mach-color
fi

(you need to adapt this for (t)csh. it checks and sees if your terminal is network, the default, and then will set it to mach-color if it is. that way if u ssh in from linux or something, it wont mess it up.

it works. giFTcurs is now in color, and the function keys still work (up
to f4 anyway)>>


Let me know if it works.


Cheers...

[AndreasG]

Hi sao,

I'm a little bit busy at the moment, so I didn't have time to try it yet... Also I have no idea _how_ to modify this for (t)csh... I'm still not too familiar with all this Unix stuff, and it will take me a few hours of reading to figure out how all this works... I just don't like doing things I don't understand... And honestly: I didn't understand very much of what Chris Zubrzycki posted ...

I will read about it and try when I have time to play around with that stuff again...

So long, Andreas