🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.sys.next.sysadmin
1 messages
1 total messages Started by Dick Silbar Mon, 05 Oct 1992 04:06
Re: why the "incomplete termcap" warning? -- RESOLVED
#1752
Author: Dick Silbar
Date: Mon, 05 Oct 1992 04:06
47 lines
1781 bytes
I had earlier written about a warning received when I logged in by
dialing in through a modem.  Art Isbell responded with a "bashful
solution", which I will not report here (since I don't know anything
about bash).  What has cured the problem for me was the response from
Pierce Cantrell (cantrell@ee.tamu.edu), and I'll take the liberty of
posting his response.  (Several others have asked for the solution).

-----------------------
From cantrell@ee.tamu.edu Sat Oct  3 12:46:13 1992

Try something like that below in your .login file. This same problem  
existed in 2.x. I am now running 3.0 with this .login as well without  
problem.

The termcap entries for terminal types of network and dialup are incomplete.
--
#
# This file gets executed once at login or window startup.
#
switch($TERM)
case network:
case dialup:
case unknown:
	unsetenv TERMCAP
	set noglob
	@ status=1
	while ($status)
		eval `tset -Q -s -m :\?vt100`
	end
	unset noglob
	set term=$TERM
	clear
	breaksw
default:
	set noglob; eval `tset -Q -s`; unset noglob
	set term=$TERM
	stty -tabs
	breaksw
endsw
stty decctlq intr "^C" erase "^?" kill "^U"
cd

--
Pierce E. Cantrell                   |  cantrell@ee.tamu.edu
-----------------------

   Dick Silbar
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads