Boyd Stephen Smith Jr. wrote:
> On Tuesday 27 February 2007, Dale <[EMAIL PROTECTED]> wrote about 'Re:
> [gentoo-user] Kwrite and CPU usage and locking up when scrolling':
>
>> Alan McKinnon wrote:
>>
>>> On Monday 26 February 2007, Dale wrot
On Tuesday 27 February 2007, Dale <[EMAIL PROTECTED]> wrote about 'Re:
[gentoo-user] Kwrite and CPU usage and locking up when scrolling':
> Alan McKinnon wrote:
> > On Monday 26 February 2007, Dale wrote:
> >> h, I have used less for a lot for things but not
Alan McKinnon wrote:
> On Monday 26 February 2007, Dale wrote:
>
>
>> 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
On Monday 26 February 2007, Mick wrote:
> On Monday 26 February 2007 20:42, Dale wrote:
> > Alan McKinnon wrote:
> > > To *look* at emerge.log, one uses less. Or more. Or most.
>
> Hmm, what is "most"? :)
An app that is supposed to be better than less, the same way that less
is better than more.
On Monday 26 February 2007, Dale wrote:
> 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 diff
On Monday 26 February 2007 20:42, Dale wrote:
> Alan McKinnon wrote:
> > To *look* at emerge.log, one uses less. Or more. Or most.
Hmm, what is "most"? :)
> > Never ever ever does one use a text editor to look at a log.
Funny that, I use rview all the time. I also use cat and pipe it to less,
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,
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 KWr
Bo Ørsted Andresen wrote:
> On Sunday 25 February 2007 13:08:34 Benno Schulenberg 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 bu
On Sunday 25 February 2007 13:08:34 Benno Schulenberg 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 an
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 lik
Willie Wong wrote:
>
> use sed, the syntax is practically the same.
>
> sed -e "s/\*\*\*//" /var/log/emerge.log > /tmp/sedemerge.log
>
> and then open /tmp/sedemerge.log using Kwrite.
>
> Best,
>
> W
>
Thanks Willie. That worked great. I wonder if someone needs to tell
the programmer for p
On Sat, Feb 24, 2007 at 07:11:46AM -0600, Penguin Lover Dale squawked:
> Benno Schulenberg wrote:
> > Open a copy of your emerge.log in vim and do:
> >
> > :%s/\*\*\*//
> >
> H, I don't have vim installed.
use sed, the syntax is practically the same.
sed -e "s/\*\*\*//" /var/log/emerge.l
Benno Schulenberg wrote:
> Dale wrote:
>
>> Here is the thing that is so odd, it will open any other
>> large file and work fine but it will mess up on emerge.log.
>>
>
> Open a copy of your emerge.log in vim and do:
>
> :%s/\*\*\*//
>
> After that KWrite will handle the file without a p
Dale wrote:
> Here is the thing that is so odd, it will open any other
> large file and work fine but it will mess up on emerge.log.
Open a copy of your emerge.log in vim and do:
:%s/\*\*\*//
After that KWrite will handle the file without a problem. As to
why, I can only guess: when the sta
Dale wrote:
>
> Well, I like nano better but not if I can use something GUI. ;-)
> That option is not exactly what I am hoping to use.
>
> I don't understand portage and ebuilds well enough to do that. How
> about this. Is there a way to just tell emerge to emerge each
> separate package and g
Boyd Stephen Smith Jr. wrote:
>
>
> Bringing kde-meta up to version 3.5.6 is going to want to upgrade ALL it's
> dependencies to 3.5.6 (which includes kate).
>
> To maintain different versions of of the various KDE packages, you'll need
> to
> remove the kde-meta package. To make sure 'emerge -
On Monday 05 February 2007 22:41, Dale wrote:
> Dale wrote:
> >> Calculating dependencies... done!
> >> [ebuild U ] kde-base/kdelibs-3.5.6-r2 [3.5.5-r7] USE="acl alsa
> >> arts cups doc fam jpeg2k spell ssl tiff -avahi -debug -kdeenablefinal
> >> -kdehiddenvisibility -kerberos -legacyssl -lua -
On Tuesday 06 February 2007, Dale wrote:
> I don't understand portage and ebuilds well enough to do that. How
> about this. Is there a way to just tell emerge to emerge each
> separate package and get rid of kde-meta?
kde-meta is, well, as meta package. All it does is tell portage to
emerge a
Alan McKinnon wrote:
> On Tuesday 06 February 2007, Dale wrote:
>
>> Dale wrote:
>>
>
> First off, I get the same behaviour this end. kwrite borks out on
> emerge.log which is about 8M. On a machine with 2G ram this should not
> happen. It does the same thing as a kpart in konqueror
>
>
On Tuesday 06 February 2007, Dale wrote:
> Dale wrote:
First off, I get the same behaviour this end. kwrite borks out on
emerge.log which is about 8M. On a machine with 2G ram this should not
happen. It does the same thing as a kpart in konqueror
> Well, I'm trying to mask this so it will not u
Dale wrote:
> < snip >
> This is what I went back too.
>
>> [EMAIL PROTECTED] / # emerge -pv kdelibs kate
>>
>> These are the packages that would be merged, in order:
>>
>> Calculating dependencies... done!
>> [ebuild U ] kde-base/kdelibs-3.5.6-r2 [3.5.5-r7] USE="acl alsa
>> arts cups doc fam
Benno Schulenberg wrote:
> Dale wrote:
>
>> Dale wrote:
>>
>>> Then I noticed that when I open a
>>> large file, like say emerge.log, that Kwrite locks up and takes
>>> my CPU to almost 100% when I try to scroll to the bottom.
>>>
>
> Same thing here. I remember seeing this bug befo
Dale wrote:
> Dale wrote:
> > Then I noticed that when I open a
> > large file, like say emerge.log, that Kwrite locks up and takes
> > my CPU to almost 100% when I try to scroll to the bottom.
Same thing here. I remember seeing this bug before, and think it
was solved at some point by an upgrad
Dale wrote:
> Hi,
>
> I noticed recently that some things have changed a bit. First I noticed
> that my fonts looked funny. They are easy to read and all but look
> different. Then I noticed that when I open a large file, like say
> emerge.log, that Kwrite locks up and takes my CPU to almost 100
Hi,
I noticed recently that some things have changed a bit. First I noticed
that my fonts looked funny. They are easy to read and all but look
different. Then I noticed that when I open a large file, like say
emerge.log, that Kwrite locks up and takes my CPU to almost 100% when I
try to scroll
26 matches
Mail list logo
