% setenv TERM "xterm-16color"To have this always be your setting, add the above line to your .tcshrc file (and create the file if necessary).
|
|
|
To get ANSI Colors in Terminal.app when running Jaguar (Mac OS X 10.2), all you need to do is open the Terminal and type:
% setenv TERM "xterm-16color"To have this always be your setting, add the above line to your .tcshrc file (and create the file if necessary).
•
[14,557 views]
Hint Options
What does this mean?
When running the command in the tip, I get the following:
RE: What does this mean?
It means that you don't have an /etc/termcap file, which is where the information about what colors to use for what comes from.
What does this mean?
I had the same problem. It turns out that for some reason os 10.2 didn't put a termcap in /usr/share/misc
Re: Missing File
Any ideas as to where everyone else can get a termcap file?
what does it do ?
i issued the cmd, but didn't see much of a difference. Which parts of terminal are supposed to get colorized ?
help setting .tcsh
Last hint of this sort (relating to the prompt) led me to make a .tcsh file. Doing so suddenly made all of my commands impossible to run (the terminal couldn't find them). I tried the .resources.mine alternative but that did nothing. Is there some trick to getting terminal settings to stick? Is there a problem with using FINK?
help setting .tcsh
no it is not a problem with Fink.
help setting .tcsh
If you created on I suggest the first line should be
help setting .tcsh
You have said, that someone sends you a working termcap-file. Is it possible to get a WORKING termcap for color in ls in the terminal under 10.2.2 from you?
what does it do ?
You can see the difference if you do a man and the subtitles will be in color
hmmm didn't work
I copied an /etc/termcap from my linux 7.2
Not xterm-16color
Please be careful to use a terminal definition entry that is valid on your system.
Not xterm-16color
How do we find which are valid with our system? Both xterm-color and xterm-16color work on my machine (seen by playing nethack), but when I use them I can't run programs on a sun unix machine I ssh into.
Not xterm-16color
This might help:
Not xterm-16color
I had to get a compile of lscolor for OS X in order to get a color ls. I should note that I've been using it since before 10.2, so I don't know if they made the default ls color or not. I also have no clue where I got the thing anymore, so don't ask. :)
screen works for me.
I set my TERM to "screen" and it works very well. I get color vim, and when I ssh to my Linux system I get color Mutt. I did not have any problems with setting it to "screen".
screen works for me.
Well if you happen to have (another) sack of gold lying around the home you'll be happy to know that the just-released bbedit 7 has rectangular selections. As per the first sentence, you'll probably not be so happy to find out the cost of the update. OUCH!
screen works for me.
I have been upgrading BBEdit since I bought the 4.0 version quite a few years ago. For the amount of time I spend in the program, the cost so far has been a bargain. For something like $300 total, I have been able to gain ENORMOUS efficiencies over something like vi (which I also use a LOT) for Perl, Java, HTML and XML development.
If they want to ask for $50 every year or year and a half, no problem by me. I've made WAY more than that off of it. Kudos to BareBones.
Mr. Sharumpe
No true ANSI on Mac yet - that I know of...
I have tried various hints, etc setting up color in terminal, termcaps, etc and have always reverted back to non-color as the terminal slowed to a crawl when asked to display a long dir listing for example. Doesn\\\'t really make any sense why it should slow down - but it definitely does.
No true ANSI on Mac yet - that I know of...
In fink, you'll find:
The fix
I published a hint about this before. YOu need to have ncurses installed, so install fink first (http://sf.net/projects/fink), and then add setenv TERM=xterm-color . to prove that it working, open dselect, and then look at the Selection screen.
A more
I had the same problem as above -- couldn't find /etc/termcap. So I just installed the OS X 10.2 Developer Tools CD that comes with OS X 10.2. Fixed the problem right up, and with the "official" files.
More on Termcap
Is everybody sure that termcap is installed with the Dev CD? I have that installed, and I get the "ain't no termcap" message, and it's not installed (in /etc/ or anywhere else). This has confounded me for some time.....
More on Termcap
Me too - no termcap here and I just did a clean install 10.2.2 and Developer Tools. No termcap warnings all the time...
no backspace in ssh'd screen...
it results with ~and GOTO illegal value in irc...
Another way.
If you've changed your terminal shell to bash rather than tcsh, you can enter the following in your ~/.bashrc file.
TERMINFO=/usr/share/terminfo TERM=color_xterm export TERMINFO TERMYou'll then get colour in lynx, dselect, etc. Remember, unless you enter the commands on the command line, you need to run: sh ~/.bashrcor logout from your terminal and start a new one. Dave
Simple Method + Screenshots
Here's my solution.
It provides colour output for the 'ls' and 'vi' commands. It worked for me with the default command shell (tcsh) from Terminal.
A couple of OSXGNU packages and two RC files is all I needed. My solution is designed for a single user, but it shouldn't be too hard to get it to adapt it to work for all users.
|
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.21 seconds |
|