Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Programming / Mac Programming / February 2005



Tip: Looking for answers? Try searching our database.

termcap $TERM type for OS X Terminal?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Michael D. Crawford - 23 Feb 2005 01:08 GMT
When I ssh into my web hosting service from the Terminal application in OS X,
the window gets all screwed up in the elm email client.  It looks just like
things do when the $TERM environment variable is set wrong.

echo $TERM both locally on my Mac and shelled into my hosting service yields
"xterm-color".  I don't have any trouble on the Mac, so I think the variable is
set correctly, but the /etc/termcap entry on my host doesn't match Terminal's
expectations.

The host is a Linux box, I think it is Slackware, and probably a recent release
but I don't know which one.

I once saw someone who had a private termcap just for himself, I think it might
have been in a $TERMCAP environment variable.  If that would work maybe someone
could give me a clue how.  I don't find a /etc/termcap file on my Mac, maybe it
uses terminfo, which I think uses a different format.

If all else fails, I could probably get my hosting service to add a new entry
for Macs to their termcap.  It's Seagull Networks (http://www.seagull.net/), run
by Paul Celestin, who many of you likely remember from his Apprentice Mac
freeware CDs.  Paul is a good guy.  I've had all my domains hosted with him
since '97.

TIA,

Michael D. Crawford
crawford@goingware.com

    Read GoingWare's Bag of Programming Tricks at:
           http://www.goingware.com/tips/
John A. Weeks III - 23 Feb 2005 01:54 GMT
> When I ssh into my web hosting service from the Terminal application in OS X,
> the window gets all screwed up in the elm email client.  It looks just like
> things do when the $TERM environment variable is set wrong.

I have been using good old "vt100" without a problem logging into
a Sun Sparc box.  There are variations of vt100 that add more
features.  You can go surfing through the termcap or terminfo
database on the destination machine.  Another one to try is
trusty old "ansi".

-john-

Signature

======================================================================
John A. Weeks III           952-432-2708            john@johnweeks.com
Newave Communications                         http://www.johnweeks.com
======================================================================

Michael D. Crawford - 23 Feb 2005 03:20 GMT
Hi,

> I have been using good old "vt100" without a problem logging into
> a Sun Sparc box.  There are variations of vt100 that add more
[quoted text clipped - 3 lines]
>
> -john-

I tried both vt100 and ansi with the same results.  I'm not completely sure if
the problem is the termcap.  What happens to me is that in elm, only some of the
message subjects are displayed, and more appear as I scroll up and down.
Possibly it is some kind of networking problem.

But, perhaps you could post the vt100 termcap from your Sparc box?  That is, if
it uses /etc/termcap.  However, it does look like that on OSX there is a tool to
convert between terminfo entries and termcap ones.

Maybe if you can give me a better config, I can figure out how to use it
privately, without having to get Paul to add it to the /etc/termcap file.

Michael D. Crawford
crawford@goingware.com

    Read GoingWare's Bag of Programming Tricks at:
          http://www.goingware.com/tips/
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.