Hello, Thanks to a suggestion by Michael Stone, I tried TERM=vt100 from the command line, and vi now seems to work properly in a telnet window. Very nice. Thank you Michael.
How can I set my login script to set TERM=vt100 *only* for telnet sessions, and not for console (or other) logins? As I understand it, the console emulates a vt220, and I don't want to lose the extra funtionality when I login at the console. TIA, --David > -----Original Message----- > From: Michael Stone [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 06, 1998 1:13 AM > To: David Karlin > Subject: »Ø¸´: Problem using vi in telnet session > > > > I am not sure about the following method, > modify the profile set of your user account, set TERm=vt100 > try it > > -----Original Message----- > From: David Karlin <[EMAIL PROTECTED]> > To: Debian User <debian-user@lists.debian.org> > Date: Tuesday, October 06, 1998 3:51 PM > Subject: Problem using vi in telnet session > > > >Hello, > >I'm running a hamm system and mostly login through a telnet window on > >my win95 machine (I have only one monitor as of yet). > > > >When I run vi in the telnet window, I get some strange behavior. Just > >about no matter which key I press, the screen blanks, and then vi > >begins to save a copy of the file. (BTW, deselect also acts strangely.) > > > >When I plug my monitor into the Linux box and login at the console, vi > works > >fine. > > > >I asked someone about this and he said it might have something to do > >with the terminal type of my telnet client. The win95 telnet client > >I'm using emulates a VT100-ansi. > > > >Has anyone experienced this kind of situation? Can anyone point me to > >the appropriate docs, or offer a solution? I looked in "Running Linux", > >but couldn't find any info there. > > > >Tia, > >--David > > > > > >-- > >Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < > /dev/null > > > > >
