From owner-freebsd-questions Fri May 26 13:47:45 2000 Delivered-To: freebsd-questions@freebsd.org Received: from web2.sea.nwserv.com (web2.sea.nwserv.com [216.145.16.2]) by hub.freebsd.org (Postfix) with ESMTP id 34CB237B7DD for ; Fri, 26 May 2000 13:47:41 -0700 (PDT) (envelope-from jim@freeze.org) Received: from localhost (jfreeze@localhost) by web2.sea.nwserv.com (8.9.3/8.9.2) with ESMTP id NAA28270; Fri, 26 May 2000 13:47:37 -0700 (PDT) (envelope-from jim@freeze.org) Date: Fri, 26 May 2000 13:47:36 -0700 (PDT) From: Jim Freeze X-Sender: jfreeze@web2.sea.nwserv.com To: Kent Stewart Cc: Christoph Sold , questions@FreeBSD.ORG Subject: Re: Help: Wierd Terminal Copy Problem In-Reply-To: <392EE137.C9FA7325@3-cities.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Envelope-To: kstewart@3-cities.com Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 May 2000, Kent Stewart wrote: > > I tried the following: > > > > vi: failed > > vim: failed > > gvim: ok > > > I do to. It may not be kvt but it does appear to be tightly related > :). I downloaded and built vim. The paste session also locked up on my > system. I don't know if locked up is a proper term because they > continue to chew up cpu time. A tight loop seemed to be obvious. > Murphy can misslead you there as to the proper terminology :). > Yes. I have been killing the kvt windows with kill -9. That seems to work. I should also mention that if I start an xterm from within a kvt window, then it works. So I get kvt-vi: failed kvt-vim: failed kvt-gvim: ok (gvim creates its own window, so maybe that's the key) xterm-vi: ok xterm-vim: ok xterm-gvim: ok I can't believe that no-one else has seen this. It is so mainstream! Thanks for corroberating this with me. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message