From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HLmoO-0004YF-Jf for garchives@archives.gentoo.org; Mon, 26 Feb 2007 20:51:09 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l1QKmhw5022630; Mon, 26 Feb 2007 20:48:43 GMT Received: from mirus.exceedtech.net (ns0.exceedtech.net [70.151.169.5]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l1QKgEhX014997 for ; Mon, 26 Feb 2007 20:42:15 GMT Received: from [65.142.88.80] (0-2pool88-80.nas1.greenwood1.ms.us.da.qwest.net [65.142.88.80]) by mirus.exceedtech.net (8.12.8/8.12.8) with ESMTP id l1QKg9v0020270 for ; Mon, 26 Feb 2007 14:42:10 -0600 Message-ID: <45E3461F.10207@exceedtech.net> Date: Mon, 26 Feb 2007 14:42:07 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20070105 SeaMonkey/1.0.7 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling References: <45C6535B.8090907@exceedtech.net> <45E0A53E.6070109@exceedtech.net> <200702251308.34928.benno.schulenberg@gmail.com> <200702262203.50051.alan@linuxholdings.co.za> In-Reply-To: <200702262203.50051.alan@linuxholdings.co.za> Content-Type: multipart/alternative; boundary="------------020809040703090205080405" X-Archives-Salt: 258627ad-e854-4f7b-9d26-9d097bd1ec8a X-Archives-Hash: 3037d72db9f0b81a1a4c853ea5ba98e2 This is a multi-part message in MIME format. --------------020809040703090205080405 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Alan McKinnon wrote: > On Sunday 25 February 2007, Benno Schulenberg wrote: > >> Dale wrote: >> >>> I wonder if someone needs to >>> tell the programmer for portage that kwrite doesn't like those >>> *** in there at all? Should I file it as a bug? >>> >> Of course not. If anything, it's a bug in KWrite. Why are you >> using KWrite anyway to look at the emerge log? Why not use >> something like Kuroo? Or else qlop (from portage-utils)? >> > > To *look* at emerge.log, one uses less. Or more. Or most. > > Never ever ever does one use a text editor to look at a log. > > However, this is almost certainly a bug in kwrite, or kwrite has been > configured to consider .log files to be some kind of sources that needs > fomatting with collapsible sections. In either event, usage of kwrite > is the wrong tool for the wrong job. > > Dale, I think you have a teeny bit of six-year-old-with-a-hammer > syndrome > > alan > > > > It may be the wrong tool, but it has always worked before. I tend to use what works. I said this in a reply somewhere before. By the time I get good at using a command, like the now extinct etcat, they change it to something else with a whole different set of options. I'm hoping things will settle down then I can learn all this once. Of course, if you wish to share a few commands with options and what they do, that may help. I'm not sure I even know what all the commands are right now. I got to much on my brain right now. It is like mush. hmmmm, I have used less for a lot for things but not files this big. I could wear out my page down key. LOL At least I don't have to look into the emerge.log very often. That's good. Thanks. Dale :-) :-) :-) :-) -- www.myspace.com/dalek1967 --------------020809040703090205080405 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id l1QKmhwJ022630 Alan McKinnon wrote: 
On Sunday 25 February 2007, Benno Schulenberg wrote:
  
Dale wrote:
    
I wonder if someone needs to
tell the programmer for portage that kwrite doesn't like those
*** in there at all?  Should I file it as a bug?
      
Of course not.  If anything, it's a bug in KWrite.  Wh=
y are you
using KWrite anyway to look at the emerge log?  Why not use
something like Kuroo?  Or else qlop (from portage-utils)?
    

To *look* at emerge.log, one uses less. Or more. Or most.

Never ever ever does one use a text editor to look at a log.

However, this is almost certainly a bug in kwrite, or kwrite has been=20
configured to consider .log files to be some kind of sources that needs=20
fomatting with collapsible sections. In either event, usage of kwrite=20
is the wrong tool for the wrong job.

Dale, I think you have a teeny bit of six-year-old-with-a-hammer=20
syndrome

alan

It may be the wrong tool, but it has always worked before.=C2=A0 I tend t= o use what works.=C2=A0 I said this in a reply somewhere before.=C2=A0 By t= he time I get good at using a command, like the now extinct etcat, they change it to something else with a whole different set of options.=C2=A0 I'm hop= ing things will settle down then I can learn all this once.

Of course, if you wish to share a few commands with options and what they do, that may help.=C2=A0 I'm not sure I even know what all the comma= nds are right now.=C2=A0 I got to much on my brain right now.=C2=A0 It is lik= e mush.

hmmmm, I have used less for a lot for things but not files this big.=C2=A0= I could wear out my page down key.=C2=A0 LOL=C2=A0 At least I don't have to= look into the emerge.log very often.=C2=A0 That's good.

Thanks.

Dale

:-)=C2=A0 :-)=C2=A0 :-)=C2=A0 :-)


--=20
www.myspace.com/dalek1967
--------------020809040703090205080405-- -- gentoo-user@gentoo.org mailing list