From michael at cadilhac.name Tue May 27 13:00:52 2014 From: michael at cadilhac.name (=?UTF-8?Q?Micha=C3=ABl_Cadilhac?=) Date: Tue, 27 May 2014 15:00:52 +0200 Subject: [Clfswm-devel] Pain caused by daily use. Message-ID: Hi there Philippe and folks; I'm reporting on my daily use of CLFSWM, on which I have two major griefs and one minor. Any help on these are very welcome. 1. This is the slowest WM I've ever used. After some hours of use, switching between two windows can take up to 8 seconds on my arguably modest laptop, and 5 seconds on a quad core "Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz". This is crazy. When I get lost in my window tree, ? and that still happens quite a lot since lots of times I just avoid creating a tree to not wait minutes to go from windows to windows ? I'm in pain and sadness. As when you burn bread in a toaster. Oh the sour pain. What can I do? (I tried nicing it.) 2. I rely on the popup console for quite a few background things (music, ssh proxy, ...). This has two main bugs. First, when it takes more than 4 seconds to pop up, the focus is not put on the console, but rather stays on the background window. Quickly removing and repopping the window usually assures that it displays quickly enough to get focused. It thus takes me a good 10 seconds and some frustration to just pause the music. Second, when there is more than one window on the screen, I have to be focused on a specific one for the console to even have a chance to get the focus. 3. When CLFSWM is started, NumLock is off. If I switch NumLock on, then the Mod key does not respond the CLFSWM way (even the mouse does not do all clfswm related commands). Same goes with CapsLock. Thanks for your help! M. From pbrochard at common-lisp.net Tue May 27 19:40:06 2014 From: pbrochard at common-lisp.net (Philippe Brochard) Date: Tue, 27 May 2014 21:40:06 +0200 Subject: [Clfswm-devel] Pain caused by daily use. In-Reply-To: (=?iso-8859-1?Q?=22Micha=EBl?= Cadilhac"'s message of "Tue, 27 May 2014 15:00:52 +0200") References: Message-ID: <8738fvqacp.fsf@common-lisp.net> Micha?l Cadilhac writes: > Hi there Philippe and folks; > Hi Micha?l, > I'm reporting on my daily use of CLFSWM, on which I have two major > griefs and one minor. Any help on these are very welcome. > First many thanks for your feedback! It's really useful for all. > 1. This is the slowest WM I've ever used. After some hours of use, > switching between two windows can take up to 8 seconds on my arguably > modest laptop, and 5 seconds on a quad core "Intel(R) Core(TM) i5-3470 > CPU @ 3.20GHz". This is crazy. When I get lost in my window tree, ? > and that still happens quite a lot since lots of times I just avoid > creating a tree to not wait minutes to go from windows to windows ? > I'm in pain and sadness. As when you burn bread in a toaster. Oh the > sour pain. What can I do? (I tried nicing it.) > Wow, this is really weird. You've a laptop at least twice more powerful than mine (acer aspire one, 1,66GHz, 1Gb ram) and I don't experience the same problems. So I think there is something wrong in your setup. First, can you tell us what is your OS, your lisp implementation, your CLX implementation and your clfswm version. Do you use xcompmgr for transparency? Do you use toolbars? Personally, I use clisp+portable clx[1] under Debian stable and always the last git version with no transparency and no toolbars. Second, once you see some lags, please can you investigate and report the CPU and memory usage of CLFSWM ? (top will be enough in a first time). > 2. I rely on the popup console for quite a few background things > (music, ssh proxy, ...). This has two main bugs. First, when it > takes more than 4 seconds to pop up, the focus is not put on the > console, but rather stays on the background window. Quickly removing > and repopping the window usually assures that it displays quickly > enough to get focused. It thus takes me a good 10 seconds and some > frustration to just pause the music. Second, when there is more than > one window on the screen, I have to be focused on a specific one for > the console to even have a chance to get the focus. > There is effectively a bug here about the focus. I'll have a look. But there is something really weird to have to wait 4 seconds to have the xterm pop up. You'll have to investigate here to. On my laptop (even on a Debian live booted from an iso image from a usb key), I get the xterm pop up nearly instantaneously. How many times does it takes to start an xterm for you with another window manager (I like icewm for comparison). > 3. When CLFSWM is started, NumLock is off. If I switch NumLock on, > then the Mod key does not respond the CLFSWM way (even the mouse does > not do all clfswm related commands). Same goes with CapsLock. > Here it's not a bug but a feature. NumLock and CapsLock are seen as modifiers. I use this sometimes with xbindkeys to have two different keys layout. If you want to always use NumLock with CLFSWM, use a program like numlockx, start it in your .xsession, .Xclients, .xwhatever and add (with-numlock) in your .clfswmrc (same thing with-capslock). If you want to use Numlock as a modifier for only some keys, you can add the :mod-2 in the modifier list. > Thanks for your help! > Please investigate and report any feedback. We have to fix your problems since I (at least) don't experience them. For other folks still there, do you have also some lags after some hours of usage as Micha?l? > M. > Philippe [1] git://github.com/sharplispers/clx.git From renaud at casenave-pere.fr Wed May 28 04:38:39 2014 From: renaud at casenave-pere.fr (=?iso-8859-1?Q?Renaud_Casenave-P=E9r=E9?=) Date: Wed, 28 May 2014 13:38:39 +0900 Subject: [Clfswm-devel] Pain caused by daily use. In-Reply-To: <8738fvqacp.fsf@common-lisp.net> (Philippe Brochard's message of "Tue, 27 May 2014 21:40:06 +0200") References: <8738fvqacp.fsf@common-lisp.net> Message-ID: <87y4xmy0ts.fsf@sandalphon.casenave.fr> Hi, On Tue, May 27 2014, Philippe Brochard wrote: > Micha?l Cadilhac writes: > >> 1. This is the slowest WM I've ever used. After some hours of use, >> switching between two windows can take up to 8 seconds on my arguably >> modest laptop, and 5 seconds on a quad core "Intel(R) Core(TM) i5-3470 >> CPU @ 3.20GHz". This is crazy. When I get lost in my window tree, ? >> and that still happens quite a lot since lots of times I just avoid >> creating a tree to not wait minutes to go from windows to windows ? >> I'm in pain and sadness. As when you burn bread in a toaster. Oh the >> sour pain. What can I do? (I tried nicing it.) >> > Wow, this is really weird. You've a laptop at least twice more powerful > than mine (acer aspire one, 1,66GHz, 1Gb ram) and I don't experience the > same problems. So I think there is something wrong in your setup. > > First, can you tell us what is your OS, your lisp implementation, your > CLX implementation and your clfswm version. Do you use xcompmgr for > transparency? Do you use toolbars? > > Personally, I use clisp+portable clx[1] under Debian stable and always the > last git version with no transparency and no toolbars. > > Second, once you see some lags, please can you investigate and report > the CPU and memory usage of CLFSWM ? (top will be enough in a first > time). clfswm may not be the fastest WM I have seen but my experience is nowhere like Micha?l's and I have "Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz" as cpu. This may be related to your graphics card, I use a GeForce GT 440 with the proprietary drivers. For a problem not directly related to clfswm (tearing in videos or in games), I tried using compton, a composition manager and it really slowed it down but I don't know if it is clfswm's fault or just a bag compton's configuration. I use sbcl and quicklisp's version of clx and git (not the latest but close enough: 2ee0a21) version of clfswm. >> 2. I rely on the popup console for quite a few background things >> (music, ssh proxy, ...). This has two main bugs. First, when it >> takes more than 4 seconds to pop up, the focus is not put on the >> console, but rather stays on the background window. Quickly removing >> and repopping the window usually assures that it displays quickly >> enough to get focused. It thus takes me a good 10 seconds and some >> frustration to just pause the music. Second, when there is more than >> one window on the screen, I have to be focused on a specific one for >> the console to even have a chance to get the focus. >> > There is effectively a bug here about the focus. I'll have a look. > But there is something really weird to have to wait 4 seconds to have > the xterm pop up. > You'll have to investigate here to. On my laptop (even on a Debian live > booted from an iso image from a usb key), I get the xterm pop up nearly > instantaneously. > How many times does it takes to start an xterm for you with another > window manager (I like icewm for comparison). Micha?l, what focus-policy do you use? I sometimes have focus problems with the :sloppy-select-window focus-policy and wanted to investigate a bit myself before reporting it here but I still haven't taken the time... Apart from that, I don't have much problem using clfswm as my main WM. -- Renaud Casenave-P?r? From thijso at gmail.com Wed May 28 06:46:56 2014 From: thijso at gmail.com (Thijs Oppermann) Date: Wed, 28 May 2014 08:46:56 +0200 Subject: [Clfswm-devel] Pain caused by daily use. Message-ID: I too do not have such problems with clfswm, although I use a bit more powerful hardware it seems. But I use it regularly on three machines, and they all work fine. My main home machine is an Intel Core i7 @ 2.67GHz from quite a few years ago, at work I use an i7 machine a little more recent, and also a very recent laptop (also a i7, not sure about the speed). The thing is, though, in all machines I have quite a bit of ram, both work machines are at 8GB, my home machine 12GB. Oh, and just remember, I also sometimes use it on my own older laptop core 2 duo with a lot less ram (1 gb? 2 maybe?), and that one works fast too with clfswm. Regards, Thijs On Wed, May 28, 2014 at 6:38 AM, Renaud Casenave-P?r? < renaud at casenave-pere.fr> wrote: > Hi, > > On Tue, May 27 2014, Philippe Brochard wrote: > > > Micha?l Cadilhac writes: > > > >> 1. This is the slowest WM I've ever used. After some hours of use, > >> switching between two windows can take up to 8 seconds on my arguably > >> modest laptop, and 5 seconds on a quad core "Intel(R) Core(TM) i5-3470 > >> CPU @ 3.20GHz". This is crazy. When I get lost in my window tree, ? > >> and that still happens quite a lot since lots of times I just avoid > >> creating a tree to not wait minutes to go from windows to windows ? > >> I'm in pain and sadness. As when you burn bread in a toaster. Oh the > >> sour pain. What can I do? (I tried nicing it.) > >> > > Wow, this is really weird. You've a laptop at least twice more powerful > > than mine (acer aspire one, 1,66GHz, 1Gb ram) and I don't experience the > > same problems. So I think there is something wrong in your setup. > > > > First, can you tell us what is your OS, your lisp implementation, your > > CLX implementation and your clfswm version. Do you use xcompmgr for > > transparency? Do you use toolbars? > > > > Personally, I use clisp+portable clx[1] under Debian stable and always > the > > last git version with no transparency and no toolbars. > > > > Second, once you see some lags, please can you investigate and report > > the CPU and memory usage of CLFSWM ? (top will be enough in a first > > time). > > clfswm may not be the fastest WM I have seen but my experience is nowhere > like > Micha?l's and I have "Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz" as cpu. > This may > be related to your graphics card, I use a GeForce GT 440 with the > proprietary > drivers. > > For a problem not directly related to clfswm (tearing in videos or in > games), I > tried using compton, a composition manager and it really slowed it down > but I > don't know if it is clfswm's fault or just a bag compton's configuration. > > I use sbcl and quicklisp's version of clx and git (not the latest but close > enough: 2ee0a21) version of clfswm. > > >> 2. I rely on the popup console for quite a few background things > >> (music, ssh proxy, ...). This has two main bugs. First, when it > >> takes more than 4 seconds to pop up, the focus is not put on the > >> console, but rather stays on the background window. Quickly removing > >> and repopping the window usually assures that it displays quickly > >> enough to get focused. It thus takes me a good 10 seconds and some > >> frustration to just pause the music. Second, when there is more than > >> one window on the screen, I have to be focused on a specific one for > >> the console to even have a chance to get the focus. > >> > > There is effectively a bug here about the focus. I'll have a look. > > But there is something really weird to have to wait 4 seconds to have > > the xterm pop up. > > You'll have to investigate here to. On my laptop (even on a Debian live > > booted from an iso image from a usb key), I get the xterm pop up nearly > > instantaneously. > > How many times does it takes to start an xterm for you with another > > window manager (I like icewm for comparison). > > Micha?l, what focus-policy do you use? I sometimes have focus problems > with the > :sloppy-select-window focus-policy and wanted to investigate a bit myself > before > reporting it here but I still haven't taken the time... > > Apart from that, I don't have much problem using clfswm as my main WM. > > -- > Renaud Casenave-P?r? > > _______________________________________________ > Clfswm-devel mailing list > Clfswm-devel at common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/clfswm-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: