🚀 go-pugleaf

In article <1934@ibmpa.UUCP> brunner@ibmsupt.UUCP () wrote:
>>In article <396@ifcom.UUCP> hst@ifcom.UUCP (Hartmut Streppel) writes:
>>If we use rlogin to login from one of the machines mentioned
>>above to the RT, and then try to use  vi on the RT, vi fails giving 
>>the message: "Don't know enough your terminal to use visual"

>The error is due to an initial sanity check in the vok routine in ex_v.c,
>the portion of the ex/vi code which checks for terminal characteristics.

>If the global WCOLS hasn't been set prior to entry into this routine,
>then there is insufficient info to divide the screen buffer into lines.

>So, why hasn't WCOLS been set? Both rlogin and telnet make an effort to
>determin the TERM shell variable in the local environment and pass it to
>the remote host, where it may be reset during the remote host login. Check
>your .cshrc/.login on the remote host for settings, you may want to have
>your term variable host dependent, set in a switch statement in .login...

Of course, the switch in .login is useless if you log in on a network
port.  I have my .kshrc prompt me for the terminal type.

It doesn't work.

The TERM variable is set to a name that has a good terminfo entry, but
vi still won't come up in full-screen mode if I open the connection with
rlogin.

When I use telnet vi works fine.


	Chuck Karish		karish@mindcraft.com
	(415) 493-9000		karish@forel.stanford.edu