TERM HOWTO: Hints and Tricks found on the net

16. Hints and Tricks found on the net

In the Linux related newsgroups many questions about TERM are coming back every couple of weeks, together with the answers to these questions. To reduce traffic to the newsgroup, in this section I shall try to make a composition of these questions and the answers to them. Some of the answers have been checked by me as I also had related problems. Others, I have just taken from the newsgroups without testing them.

Many people, especially those who are using Ultrix, seem to have trouble with vi presenting less than 24 lines on a window with 24 lines. There are three ways to get rid of this problem:
1. Log in into the remote system using:
```
  trsh -s telnet <hostname>
```
2. Put 'resize; clear' in your '.login' file
3. The best solutions seems to be to enter the following remote:
```
  stty 38400
```
Many people seem to have problems with crashing TERM connections, whatever may be the reason of the crashes. So before starting applications people want to know whether their TERM connection is still alive or not. This can be checked using the following small shell script examples: When you are using tcsh:
```
  if ( { trsh -s true } ) then
    ...
  endif
```
When you are using bash:
```
  if trsh -s true; then
    ...
  fi
```

The WWW browser Netscape is causing people problems to get it to work with TERM. The good news is that it will work under TERM. Here is how:

        1. Termify netscape
        2. Fire up termnetscape
              under Options | Preferences | Mail/Proxys
              leave _all_ of the proxy boxes blank
              set the SOCKS box to 'remotehost' & 80
        3. Ignore the error you get when you exit the Options menu.
        4. If termnetscape fails to work right:
              under Options | Preferences | Mail/Proxys
              leave _all_ of the proxy boxes blank
              set the SOCKS box to 'none' & 80
        5. Ignore the error you get when you exit the Options menu.

Scott Blachowicz mailed me stating that it is even easier to get Netscape or any other browser to work with TERM if you have a proxy server (e.g. CERN's httpd) installed for use on the remote side of your TERM link. On the local side, you can then do this:

        1. tredir localhost:8080 remotehost:80

              where 'remotehost' is the hostname of your proxy server system.

        2. Run your particular browser, then in the preferences or options or
              whatever it is called, point your proxies at 'localhost' port
              8080.
              Some browsers might like environment variables like

                  export http_proxy=http://localhost:8080/
                  export ftp_proxy=http://localhost:8080/