[gentoo-user] Kwrite and CPU usage and locking up when scrolling

[gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Dale]

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 to the bottom.  It does not respond at all after that.  I
have let it sit there for about 5 minutes with nothing changing.  If I
change desktops, it doesn't even redraw the screen for Kwrite.  It does
for the programs underneath it but not Kwrite itself.

I also ran kwrite from the command line.  I opened the same files and it
does the same thing.  I don't get any error messages though. 

Anybody have any ideas on this?  Can someone try this on their machine
and see what theirs does?  As far as my rig goes, it is a AMD 2500+ with
1GB of ram.  This worked until a week or so ago.  It seemed to start
when KDE 3.5.6 was upgraded.  I sort of suspect me though.  I may have
something wrong here.

Here is some more info:

> root@smoker / # emerge -vp kdelibs kate
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild   R   ] kde-base/kdelibs-3.5.6-r2  USE="acl alsa arts cups doc
> fam jpeg2k spell ssl tiff -avahi -debug -kdeenablefinal
> -kdehiddenvisibility -kerberos -legacyssl -lua -openexr -utempter
> -xinerama -zeroconf" LINGUAS="-he" 0 kB
> [ebuild   R   ] kde-base/kate-3.5.6  USE="arts -debug -kdeenablefinal
> -kdehiddenvisibility -xinerama" 0 kB
>
> Total size of downloads: 0 kB
> root@smoker / #

> root@smoker / # emerge --info
> Portage 2.1.1-r2 (default-linux/x86/2006.1/desktop, gcc-4.1.1,
> glibc-2.4-r4, 2.6.18-gentoo-r6 i686)
> =================================================================
> System uname: 2.6.18-gentoo-r6 i686 AMD Athlon(tm) XP 2500+
> Gentoo Base System version 1.12.6
> Last Sync: Sun, 04 Feb 2007 05:20:01 +0000
> distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port
> 3632) [disabled]
> ccache version 2.4 [enabled]
> app-admin/eselect-compiler: [Not Present]
> dev-java/java-config: 1.3.7, 2.0.31
> dev-lang/python:     2.4.3-r4
> dev-python/pycrypto: 2.0.1-r5
> dev-util/ccache:     2.4-r6
> dev-util/confcache:  [Not Present]
> sys-apps/sandbox:    1.2.17
> sys-devel/autoconf:  2.13, 2.61
> sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2,
> 1.10
> sys-devel/binutils:  2.16.1-r3
> sys-devel/gcc-config: 1.3.14
> sys-devel/libtool:   1.5.22
> virtual/os-headers:  2.6.17-r2
> ACCEPT_KEYWORDS="x86"
> AUTOCLEAN="yes"
> CBUILD="i686-pc-linux-gnu"
> CFLAGS="-march=athlon-xp -O2 -momit-leaf-frame-pointer"
> CHOST="i686-pc-linux-gnu"
> CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
> /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
> CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf
> /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c"
> CXXFLAGS="-march=athlon-xp -O2 -momit-leaf-frame-pointer"
> DISTDIR="/usr/portage/distfiles"
> FEATURES="autoconfig buildpkg ccache distlocks fixpackages
> metadata-transfer parallel-fetch sandbox sfperms strict"
> GENTOO_MIRRORS="http://adelie.polymtl.ca/
> http://gentoo.arcticnetwork.ca/ http://gentoo.mirrors.tera-byte.com/
> http://gentoo.osuosl.org/
> http://distro.ibiblio.org/pub/linux/distributions/gentoo/
> http://www.gtlib.gatech.edu/pub/gentoo
> http://ftp.ucsb.edu/pub/mirrors/linux/gentoo/
> http://gentoo.chem.wisc.edu/gentoo/ http://cudlug.cudenver.edu/gentoo/
> http://gentoo.mirrors.pair.com/ http://gentoo.mirrors.tds.net/gentoo
> http://gentoo.netnitco.net http://mirror.espri.arizona.edu/gentoo/
> http://mirrors.acm.cs.rpi.edu/gentoo/
> http://open-systems.ufl.edu/mirrors/gentoo "
> LDFLAGS="-Wl,-z,now"
> LINGUAS="en"
> MAKEOPTS="-j3"
> PKGDIR="/usr/portage/packages"
> PORTAGE_RSYNC_EXTRA_OPTS="--timeout=600"
> PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times
> --compress --force --whole-file --delete --delete-after --stats
> --timeout=600 --exclude='/distfiles' --exclude='/local'
> --exclude='/packages'"
> PORTAGE_TMPDIR="/var/tmp"
> PORTDIR="/usr/portage"
> SYNC="rsync://209.189.242.21/gentoo-portage"
> USE="x86 3dnow X acl acpi alsa alsa_cards_ali5451 alsa_cards_als4000
> alsa_cards_atiixp alsa_cards_atiixp-modem alsa_cards_bt87x
> alsa_cards_ca0106 alsa_cards_cmipci alsa_cards_emu10k1x
> alsa_cards_ens1370 alsa_cards_ens1371 alsa_cards_es1938
> alsa_cards_es1968 alsa_cards_fm801 alsa_cards_hda-intel
> alsa_cards_intel8x0 alsa_cards_intel8x0m alsa_cards_maestro3
> alsa_cards_trident alsa_cards_usb-audio alsa_cards_via82xx
> alsa_cards_via82xx-modem alsa_cards_ymfpci alsa_pcm_plugins_adpcm
> alsa_pcm_plugins_alaw alsa_pcm_plugins_asym alsa_pcm_plugins_copy
> alsa_pcm_plugins_dmix alsa_pcm_plugins_dshare alsa_pcm_plugins_dsnoop
> alsa_pcm_plugins_empty alsa_pcm_plugins_extplug alsa_pcm_plugins_file
> alsa_pcm_plugins_hooks alsa_pcm_plugins_iec958 alsa_pcm_plugins_ioplug
> alsa_pcm_plugins_ladspa alsa_pcm_plugins_lfloat
> alsa_pcm_plugins_linear alsa_pcm_plugins_meter alsa_pcm_plugins_mulaw
> alsa_pcm_plugins_multi alsa_pcm_plugins_null alsa_pcm_plugins_plug
> alsa_pcm_plugins_rate alsa_pcm_plugins_route alsa_pcm_plugins_share
> alsa_pcm_plugins_shm alsa_pcm_plugins_softvol amd arts artswrappersuid
> automount berkdb bitmap-fonts browserplugin bzip2 cairo cddb cdr
> chroot cli cracklib crypt cups dbus dlloader doc dri dvd dvdr eds
> elibc_glibc emboss encode esd exif fam fdftk fortran gaim gcj gdbm gif
> gimp gimpprint gkrellm gphoto2 gpm gstreamer gtk hal hbci iconv
> input_devices_keyboard input_devices_mouse ipv6 isdnlog java
> javascript jbig jpeg jpeg2k justify kde kernel_linux
> lcd_devices_bayrad lcd_devices_cfontz lcd_devices_cfontz633
> lcd_devices_glk lcd_devices_hd44780 lcd_devices_lb216
> lcd_devices_lcdm001 lcd_devices_mtxorb lcd_devices_ncurses
> lcd_devices_text ldap libg++ linguas_en logrotate mad midi mikmod mmx
> mp3 mpeg ncurses nptl nptlonly nsplugin offensive ofx ogg opengl pam
> pcre pdf perl png ppds pppd python qt3 qt4 quicktime readline
> reflection scanner sdl seamonkey session spell spl sqlite sse ssl
> syslog tcl tcpd tiff tk truetype truetype-fonts type1-fonts udev
> unicode usb userland_GNU video_cards_nvidia vorbis win32codecs wma wmf
> xml xorg xprint xv yahoo zlib"
> Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL,
> PORTDIR_OVERLAY
>
> root@smoker / #

I need to sort through that USE crap.  Looks like some sounds stuff has
changed.

Open to ideas.

Thanks

Dale

:-)  :-)  :-)  :-)




-- 
www.myspace.com/dalek1967

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Boyd Stephen Smith Jr.]

[-- Attachment #1: Type: text/plain, Size: 3313 bytes --]

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 -openexr -utempter
> >> -xinerama -zeroconf" LINGUAS="-he" 15,186 kB
> >> [ebuild     U ] kde-base/kate-3.5.6 [3.5.5-r1] USE="arts -debug
> >> -kdeenablefinal -kdehiddenvisibility -xinerama" 23,589 kB
> >
> > That version works fine.
> 
> Well, I'm trying to mask this so it will not upgrade when I do updates.
> I must be missing something here.  When I did the pretend downgrade it
> pulled kdelibs down one version too.  So I want to make it so that
> kdelibs and kate will stay at 3.5.5 versions.  This is what I added to
>
> package.mask:
> > =kde-base/kate-3.5.6
> > =kde-base/kdelibs-3.5.6-r2
>
> That way if there is a new release it will upgrade and hopefully it will
> be fixed.  However, this is what happens when I check for updates:
> > root@smoker / # emerge -uvDp world
> >
> > These are the packages that would be merged, in order:
> >
> > Calculating world dependencies \
> > !!! All ebuilds that could satisfy "~kde-base/kate-3.5.6" have been
> > masked.
> > !!! One of the following masked packages is required to complete your
> > request:
> > - kde-base/kate-3.5.6 (masked by: package.mask)
> >
> > For more information, see MASKED PACKAGES section in the emerge man
> > page or
> > refer to the Gentoo Handbook.
> > (dependency required by "kde-base/kdebase-meta-3.5.6" [ebuild])
> >
>
> Do I need to mask kde-meta too or is there some other way around this??
> < scratches head >

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 -u world' (or a 
variant), 
pulls in new version of other packages, you'll want to 'emerge -n' the 
various direct dependencies of kde-meta (kdenetwork-meta etc).

I doubt kate is a direct dependency of kde-meta (I could be wrong).  If it 
isn't, one (or more) of the other kde${stuff}-meta packages will also try 
to 
upgrade it.  Instead of 'emerge -n'-ing those packages, 'emerge -n' it's 
direct dependencies (one of which should be kate).

You may actually find some packages that you don't care about, feel free to 
not 'emerge -n' them.  They will then not be updated by an 'emerge -u 
world' 
and my be removed be 'emerge --depclean' (unless they are a dependency of 
some other package in world)

In fact, I recently removed all the kde${stuff}-meta packages from my 
system 
and only installed the KDE applications I wanted.  This might result in 
significant disk space savings, but YMMV.  I now have ~90 packages from the 
kde-base category instead of the ~350 pulled in by kde-meta.

-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss03@volumehost.net                      ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.org/                      \_/     
New GPG Key!  Old key expires 2007-03-25.  Upgrade NOW!

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]

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 -u world' (or a 
> variant), 
> pulls in new version of other packages, you'll want to 'emerge -n' the 
> various direct dependencies of kde-meta (kdenetwork-meta etc).
>
> I doubt kate is a direct dependency of kde-meta (I could be wrong).  If it 
> isn't, one (or more) of the other kde${stuff}-meta packages will also try 
> to 
> upgrade it.  Instead of 'emerge -n'-ing those packages, 'emerge -n' it's 
> direct dependencies (one of which should be kate).
>
> You may actually find some packages that you don't care about, feel free to 
> not 'emerge -n' them.  They will then not be updated by an 'emerge -u 
> world' 
> and my be removed be 'emerge --depclean' (unless they are a dependency of 
> some other package in world)
>
> In fact, I recently removed all the kde${stuff}-meta packages from my 
> system 
> and only installed the KDE applications I wanted.  This might result in 
> significant disk space savings, but YMMV.  I now have ~90 packages from the 
> kde-base category instead of the ~350 pulled in by kde-meta.
>
>   

Well, I am doing this the hard way right now.  I just check for updates
and update everything but kdelibs and kate manually.  So far, so good. 
Maybe it will get sorted soon.

Thanks

Dale

:-)  :-)  :-)  :-)

-- 
www.myspace.com/dalek1967


[-- Attachment #2: Type: text/html, Size: 2053 bytes --]

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

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 get rid of kde-meta?  I don't know, equery list
> kde then poke them in one by one.  Would that let it leave kate and
> kdelibs where it is without masking all of kde?
>
> Thanks for the reply though.  At least I can open the file and read it
> and it is not just me having this problem.
>
> Dale
>
> :-)  :-)  :-)  :-)
>
> -- 
> www.myspace.com/dalek1967
>   

OK.  I upgraded again and this time I was trying a few other files. 
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.  My messages file is larger
than my emerge.log file but it even opens fine.  I would assume it is
not the size of the file that is causing the problem.

Why is it that it will work on everything else I have tried but not my
emerge.log file??

Just curious. 

Dale

:-)  :-)  :-)  :-)

-- 
www.myspace.com/dalek1967


[-- Attachment #2: Type: text/html, Size: 1945 bytes --]

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Benno Schulenberg]

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 stars are still there, KWrite shows 
folding markers, so it sees the file as some kind of code and tries 
to "format" it, arrange it in paragraphs, and sometime searches the 
entire file in vain for some matching paragraph-closing element.  
When the stars are gone, it sees the file as plain text and doesn't 
do any searching.

Benno
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]

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 problem.  As to 
> why, I can only guess: when the stars are still there, KWrite shows 
> folding markers, so it sees the file as some kind of code and tries 
> to "format" it, arrange it in paragraphs, and sometime searches the 
> entire file in vain for some matching paragraph-closing element.  
> When the stars are gone, it sees the file as plain text and doesn't 
> do any searching.
>
> Benno
>   

Hmmmm, I don't have vim installed.  It appears that it will pull in a
good bit of dependancies too.  Is there another way to do this?  I'm on
dial-up and it will take a good while just to download all it needs to
install.

What you are saying makes sense though.  As soon as I try to scroll
down, it locks right up.

Thanks.

Dale

:-)  :-)  :-)

-- 
www.myspace.com/dalek1967


[-- Attachment #2: Type: text/html, Size: 1691 bytes --]

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Willie Wong]

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/\*\*\*// 
> >
> Hmmmm, I don't have vim installed. 

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
-- 
Occam's Eraser: The philosophical principle that even the simplest
  solution is bound to have something wrong with it.
Sortir en Pantoufles: up 78 days, 14:05
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Dale]

[-- Attachment #1: Type: text/plain, Size: 567 bytes --]

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 portage that kwrite doesn't like those *** in there
at all?  Should I file it as a bug?  I mean, kwrite is all I use unless
the GUI is borked and I have to use CL.  Then I use nano.  Sorry.  :-(

Thanks again.

Dale 

:-)  :-)  :-)  :-)

-- 
www.myspace.com/dalek1967


[-- Attachment #2: Type: text/html, Size: 1100 bytes --]

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Benno Schulenberg]

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)?

Benno
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 458 bytes --]

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 anyway to look at the emerge log?  Why not use
> something like Kuroo?  Or else qlop (from portage-utils)?

Or app-portage/genlop.

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Dale]

[-- Attachment #1: Type: text/plain, Size: 986 bytes --]

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 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)?
>>     
>
> Or app-portage/genlop.
>
>   

I'll get you both at the same time.  It seems every time I get good at a
tool, they change it to something else.  Just as I was getting good at
etcat, it went away.  So I just use Kwrite and the find feature.  It
works.  LOL  I never heard of Kuroo.  I'll have to look into that.  I
don't think I have ever seen qlop either.  O_O  The only genlop option I
have used is genlop -c. 

Sort of strange huh??

Dale

:-)  :-)  :-)  :-)

-- 
www.myspace.com/dalek1967


[-- Attachment #2: Type: text/html, Size: 1644 bytes --]

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Alan McKinnon]

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



-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty, 
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]

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


[-- Attachment #2: Type: text/html, Size: 2499 bytes --]

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Mick]

[-- Attachment #1: Type: text/plain, Size: 494 bytes --]

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, or 
just use less.  I definitely use rview.  On an average size file I don't 
really see a difference from using less.

What's wrong with using a text editor?
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Alan McKinnon]

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 different set of options.
>  I'm hoping things will settle down then I can learn all this once.

kwrite is an editor designed to edit smallish files, similar but 
slightly better than notepad. Like all small editors, it probably loads 
the entire file into memory before displaying it, and it gets very 
confused with some contents, thinking that they are blocks of code that 
can be collapsed.

The program landscape will never settle down and leave you with a 
definite set of programs - Linux lives, breathes, grows and evolves 
almost exactly the way human societies do - always changing, always 
adapting and never the same in any two places.

A few base programs you can rely on though - like less. It's a file 
viewer, designed to make it easy for you to look at the contents of 
files. It's also the thing that displays man pages. I highly recommend 
spending the few minutes it takes to get used to using it. It runs from 
a terminal, which is also worth spending some time to get used to it.

> 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.

big files the size of emerge.log (8M on my machine) is exactly what less 
excels at. The most useful key is of course "/" which lets you enter a 
string of text to search for, then 'q" to quit and "h" displays a help 
screen

alan


-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Alan McKinnon]

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. It never caught on though


alan

-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Dale]

[-- Attachment #1: Type: text/plain, Size: 2538 bytes --]

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 something else with a whole different set of options.
>>  I'm hoping things will settle down then I can learn all this once.
>>     
>
> kwrite is an editor designed to edit smallish files, similar but 
> slightly better than notepad. Like all small editors, it probably loads 
> the entire file into memory before displaying it, and it gets very 
> confused with some contents, thinking that they are blocks of code that 
> can be collapsed.
>
> The program landscape will never settle down and leave you with a 
> definite set of programs - Linux lives, breathes, grows and evolves 
> almost exactly the way human societies do - always changing, always 
> adapting and never the same in any two places.
>
> A few base programs you can rely on though - like less. It's a file 
> viewer, designed to make it easy for you to look at the contents of 
> files. It's also the thing that displays man pages. I highly recommend 
> spending the few minutes it takes to get used to using it. It runs from 
> a terminal, which is also worth spending some time to get used to it.
>   

I use a terminal a lot.  I use less pretty often too.  It's just that I
got used to Kwrite and it was working fine for me.  I don't knock what
is working.  ;-)  I always use man to display man pages.  Am I weird?

>   
>> 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.
>>     
>
> big files the size of emerge.log (8M on my machine) is exactly what less 
> excels at. The most useful key is of course "/" which lets you enter a 
> string of text to search for, then 'q" to quit and "h" displays a help 
> screen
>
> alan
>
>
>   

My thing is getting to the bottom of the page in one key stroke.  Maybe
I need to man less and read a bit.  :/

Oh well, time to learn something I guess.  It seems Kwrite is off the
path for a while.

Dale

:-)  :-)  :-)  :-)

-- 
www.myspace.com/dalek1967


[-- Attachment #2: Type: text/html, Size: 3359 bytes --]

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Boyd Stephen Smith Jr.]

[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]

On Tuesday 27 February 2007, Dale <dalek@exceedtech.net> wrote about 'Re: 
[gentoo-user] Kwrite and CPU usage and locking up when scrolling':
> Alan McKinnon wrote:
> > On Monday 26 February 2007, Dale wrote:
> >> hmmmm, I have used less for a lot for things but not files this big.
> >>  I could wear out my page down key.
> >
> > big files the size of emerge.log (8M on my machine) is exactly what
> > less excels at. The most useful key is of course "/" which lets you
> > enter a string of text to search for, then 'q" to quit and "h"
> > displays a help screen

'

Close your single-quotes man! You've turned the rest of your post into a 
non-interpolated string! ;)

> My thing is getting to the bottom of the page in one key stroke.  Maybe
> I need to man less and read a bit.  :/

I believe 'G' should do this.

-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss03@volumehost.net                      ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.org/                      \_/     
New GPG Key!  Old key expires 2007-03-25.  Upgrade NOW!

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Kwrite and CPU usage and locking up when scrolling

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]

Boyd Stephen Smith Jr. wrote:
> On Tuesday 27 February 2007, Dale <dalek@exceedtech.net> wrote about 'Re: 
> [gentoo-user] Kwrite and CPU usage and locking up when scrolling':
>   
>> Alan McKinnon wrote:
>>     
>>> On Monday 26 February 2007, Dale wrote:
>>>       
>>>> hmmmm, I have used less for a lot for things but not files this big.
>>>>  I could wear out my page down key.
>>>>         
>>> big files the size of emerge.log (8M on my machine) is exactly what
>>> less excels at. The most useful key is of course "/" which lets you
>>> enter a string of text to search for, then 'q" to quit and "h"
>>> displays a help screen
>>>       
>
> '
>
> Close your single-quotes man! You've turned the rest of your post into a 
> non-interpolated string! ;)
>
>   
>> My thing is getting to the bottom of the page in one key stroke.  Maybe
>> I need to man less and read a bit.  :/
>>     
>
> I believe 'G' should do this.
>
>   

I did what with quotes?

'G', that works.  I sort of got two out of one on that one.  LOL

Dale

:-)  :-)  :-)  :-)

-- 
www.myspace.com/dalek1967


[-- Attachment #2: Type: text/html, Size: 1953 bytes --]