Date: Wed, 27 May 1998 20:42:22 -0500 From: "Mike Grommet" <mgrommet@insolwwb.net> To: <djv@bedford.net> Cc: <freebsd-questions@FreeBSD.ORG> Subject: Re: Clear command locks up telnet window? Message-ID: <009701bd89d9$dc259140$0cf896d0@work1.insolwwb.net>
next in thread | raw e-mail | index | archive | help
Well, I am attempting to change the termcap entry for freebsd to remove this padding... the machine is rebooting as I type this... I should know more shortly. Hm... apparently that didnt make a difference... I modified the termcap entry for vt100 and it still did it, do I need to do anything after I modify termcap to make the changes take effect? BTW, if I use a terminal prog that supports vt220 it works fine... go figure. -----Original Message----- From: CyberPeasant <djv@lucy.bedford.net> To: Mike Grommet <mgrommet@insolwwb.net> Date: Wednesday, May 27, 1998 5:34 PM Subject: Re: Clear command locks up telnet window? >Mike Grommet wrote >[Charset iso-8859-1 unsupported, filtering to ASCII...] >> it worked fine... I'm really stumped here. > >Yeah. I looked at the termcap entry for vt100 on BSD >and it is moderately different from the one on OpenBSD (the >other OS I have handy here.) The difference is that the >F'BSD entry has lots of padding all over it. > >The cl sequence (clear screen and home cursor, if you've been spared >the joys of termcap so far) of interest are: > > FreeBSD: 50\E[H\E[J > OpenBSD: \E[H\E[J > > FreeBSD: \E[H\E[J for xterm > >Soooo... you tell me :) how 50ms of padding is hosing a telnet connection. >For one thing, over telnet, you don't need any #$#$ padding, which is just >for the purpose of allowing a "real" vt100 to burp and clear its screen. > >Maybe the fix is to use "vs100" (i.e. xterm) for TERM/term? > >(... more on this later ...) > >Dave > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?009701bd89d9$dc259140$0cf896d0>