Date: Sun, 29 Dec 1996 21:15:39 -0500 (EST) From: Keith Bostic <bostic@bsdi.com> To: davidn@sdev.usn.blaze.net.au Cc: hackers@freebsd.org, jkh@time.cdrom.com, kimc@w8hd.org Subject: Re: David Nugent: Re: vi edit mode unstable -termcap ? Message-ID: <199612300215.VAA23937@mongoose.bostic.com>
next in thread | raw e-mail | index | archive | help
> From: davidn@sdev.usn.blaze.net.au (David Nugent) > > Kim Culhan writes: >> I have had this problem here for some time, searched for the cause today >> and cannot find it. >> >> On two -current machines here, when using an xterm and telnet to the other >> machine, when using the arrow-keys to move around the screen, vi will >> switch to the insert mode and deposit characters into the editor. >> >> For example if I hit the down-arrow key a few times, after about >> 3 or 4 arrow-down, it will begin to put 'B' into the editor. > > Yes, this is really VERY annoying. I have the same problem with > any network connections, even across 10mb ethernet, which is just > plain crazy. The workaround (and it IS only a workaround!) is to > put set escapetime=10 into ~/.exrc. Actually, it's not a workaround, that's exactly what it's intended for! ;-} > Could the maintainer of nvi PLEASE use a more reasonable default > value for escapetime? This is problematic even editing in an xterm > locally on a system running under a reasonable load. I'm happy to make the change, I do very little remote editing, so I just don't see the problem. What's a good value to use? >> On a third machine running 2.2-current from 9-15 I can telnet to it >> from either of the other machines and it will not do this. > > This started with the recent vendor import of the new version > of nvi. "split" disappeared too. :-( Actually, split was replaced. You can now capitalize most (all?) of the standard operations and they'll happen in a split screen. So, E[dit], T[ag], N[ext], P[rev] etc. all work in a split screen. (It's all documented in the reference guide, too, if you want further information.) --keith
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612300215.VAA23937>