Re: getting "dumb" terminal message in Unix shell

[nparker@cie-2.uoregon.edu (Neil Parker)]

In article <5ing7n$s8c$2@news.vanderbilt.edu>
NO%lesh%SPAM%erjt%HERE@vuse.vanderbilt.edu (Tilghman Lesher) writes:
>Neil Parker (nparker@cie-2.uoregon.edu) wrote:
>
>: (replace the word "(username)" by your user name--for example, my username
>: is "nparker", so I would type "grep nparker /etc/passwd").  Look at the
>: very end of the response.  If the last word of the response is "csh" or
>: "tcsh", type the following:
>
>:      set term=vt100
>
>Should be:	setenv TERM vt100

On the contrary, "set term=vt100" does the job just fine on all the csh versions
I've ever tried it with.  In csh, the shell variable "term" is "magic"--
whenever you change it, the environment variable "TERM" is automatically
changed to match.

>: If you succeed in getting one of those commands to work, you can make the
>: setting permanent by putting it in your logon script.  The csh/tcsh command
>: should be put into a file called ".login", 
>
>or .cshrc

For setting options (such as the terminal type) that only need to be set
once per session, .login is usually a better place to put it.  Remember,
.cshrc runs not only when you log on, but also every time you start a
subshell.  So .cshrc is a good place to put things (like aliases) that
normally aren't inherited automatically by subshells.


But we're getting a bit far afield from the Apple II here.  If you want to
debate UNIX shell configuration philosophies, we should probably take it to
e-mail.

            - Neil Parker
-- 
Neil Parker, nparker@{cie-2,cie}.uoregon.edu, http://cie-2.uoregon.edu/~nparker
     "Evolution is vastly overrated."  -- Ambassador Delenn, _Babylon_5_

Unsolicited commercial e-mail to my address will be discarded unread.