Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!elroy.jpl.nasa.gov!jarthur!petunia!csuchico.edu!mrush
From: mrush@ecst.csuchico.edu (Matt "C P." Rush)
Newsgroups: comp.sys.next
Subject: Why did 2.0 munge telnet?
Message-ID: <1991Apr03.025943.14365@ecst.csuchico.edu>
Date: 3 Apr 91 02:59:43 GMT
Sender: news@ecst.csuchico.edu (USENET)
Organization: California State University, Chico
Lines: 18


	I just installed 2.0 on our '030 cube, and have run into a rather
annoying problem.  It seems that when logging into the NeXT from a vt100
emulation, ksh no longer scrolls through the command history correctly.
	BEFORE 2.0 you could press 'esc' and then 'k' would display the
previous command line.  Press 'k' again and you get the command line before
that, etc.
	NOW if you press 'esc' and then 'k' the line remains blank.  If you
continue pressing 'k' you start getting k's on your input line.  If you just
do 'esc' 'k' ONCE, and press return, the previous command line is re-executed.

	Since this problem only seems to occur under 'telnet' I have to assume
that 'telnet' is changed under 2.0.  Since this behaviour renders telnet darn
well useless, WHAT was changed, does it NEED to be changed, and can I get away
with running 1.0 telnet under 2.0?

	-- C P.
	mrush@cscihp.ecst.csuchico.edu