From owner-freebsd-questions Fri May 26 14:16:34 2000 Delivered-To: freebsd-questions@freebsd.org Received: from corinth.bossig.com (corinth.bossig.com [208.26.239.66]) by hub.freebsd.org (Postfix) with ESMTP id 3FB6637B852 for ; Fri, 26 May 2000 14:16:27 -0700 (PDT) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (unverified [208.26.242.65]) by corinth.bossig.com (Rockliffe SMTPRA 4.2.1) with ESMTP id ; Fri, 26 May 2000 14:16:43 -0700 Message-ID: <392EE99B.A14EB3BE@3-cities.com> Date: Fri, 26 May 2000 14:16:11 -0700 From: Kent Stewart Organization: BOSSig X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Jim Freeze Cc: Christoph Sold , questions@FreeBSD.ORG Subject: Re: Help: Wierd Terminal Copy Problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Freeze wrote: > > 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. The fact that you don't end up with a vi recovery file in /tmp is remarkable here :). > 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! It only seemed to be the ls that caused the problem. I could copy test from a file just fine. You may have some hidden control characters because of kvt that are causing the problems. They are busy developing kde2 and probably wouldn't spend the time to figure out what was causing the problem. It would be interesting if kde2 has the same problem because it is much more likely to get fixed there. > > Thanks for corroberating this with me. I joke that I am a lightening rod for bugs. If a product has 3 or more, I'm sure I will see one of them. BTW, why is the blank cc showing up on your message. It seems to cause two copies to end up on -questions. Kent > > Jim -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message