On Tue, Aug 17, 2010 at 1:39 PM, Marco Peereboom sl...@peereboom.us wrote:
I bet that is the controlled shut down where applications create windows
and then destroy them before scrotwm can focus on them. B I fixed this in
cvs and would appreciate a test report. B CVS instructions are on the www
no it isn't. the external version isn't the same as the cvs version.
obviously we don't change the external version after every commit.
use m-s-v for the real version.
On Thu, Aug 19, 2010 at 10:32:38AM +0200, Tomas Bodzar wrote:
On Tue, Aug 17, 2010 at 1:39 PM, Marco Peereboom
On Thu, Aug 19, 2010 at 1:53 PM, Marco Peereboom sl...@peereboom.us wrote:
no it isn't. B the external version isn't the same as the cvs version.
obviously we don't change the external version after every commit.
use m-s-v for the real version.
Welcome to scrotwm V0.9.25 cvs tag: $scrotwm:
On Tue, Aug 17, 2010 at 10:20:23PM +0200, Jiri B. wrote:
On Tue, 17 Aug 2010 06:40:21 -0500
Marco Peereboom sl...@peereboom.us wrote:
dmesg?
I have to first eliminate potential involvement of i/o slowdown because
of big use of softraid (i have everything except '/' on softraid).
On
On Tue, Aug 17, 2010 at 10:56:58AM -0400, Ted Unangst wrote:
On Tue, Aug 17, 2010 at 3:30 AM, Tomas Bodzar tomas.bod...@gmail.com wrote:
did someone saw similar problem in scrotwm(1)? Eg. when I start
xeyes(1) on empty workspace from menu M-p it simply shut down X. If
I start eg. xcalc(1)
On 08/18/10 14:02, Owain Ainsworth wrote:
...
As a note, scotwm really needs it own mailing list, scrotwm bugs are not
really topical for misc.
and a graphic! don't forget a graphi...er..hmmm
Maybe that wouldn't be such a good idea.
Nick.
On 19 August 2010 01:07, Nick Holland n...@holland-consulting.net wrote:
On 08/18/10 14:02, Owain Ainsworth wrote:
...
As a note, scotwm really needs it own mailing list, scrotwm bugs are not
really topical for misc.
and a graphic! don't forget a graphi...
Here you go:
Nick Holland wrote on Wed, Aug 18, 2010 at 07:07:14PM -0400:
On 08/18/10 14:02, Owain Ainsworth wrote:
As a note, scotwm really needs it own mailing list,
and a graphic! don't forget a graphi...er..hmmm
Maybe that wouldn't be such a good idea.
Why? What's wrong with a graphic for
On Wed, Aug 18, 2010 at 5:18 PM, ropers rop...@gmail.com wrote:
Here you go:
http://i.imgur.com/Bns7H.png
I lol'd.
On Wed, Aug 18, 2010 at 8:18 PM, ropers rop...@gmail.com wrote:
On 19 August 2010 01:07, Nick Holland n...@holland-consulting.net wrote:
On 08/18/10 14:02, Owain Ainsworth wrote:
...
As a note, scotwm really needs it own mailing list, scrotwm bugs are not
really topical for misc.
and a
Hi all,
did someone saw similar problem in scrotwm(1)? Eg. when I start
xeyes(1) on empty workspace from menu M-p it simply shut down X. If
I start eg. xcalc(1) then everything is ok. Another problem is with
xlock(1). When I want to lock my screen and start xlock(1) eg. this
way 'xlock -mode
On Tue, Aug 17, 2010 at 09:30:57 +0200, Tomas Bodzar wrote:
Hi all,
did someone saw similar problem in scrotwm(1)? Eg. when I start
xeyes(1) on empty workspace from menu M-p it simply shut down X.
Wish I hadn't tried it :) Yes, it happens here too.
[...]
So someone here with similar
did someone saw similar problem in scrotwm(1)? Eg. when I start
xeyes(1) on empty workspace from menu M-p it simply shut down X. If
I start eg. xcalc(1) then everything is ok. Another problem is with
xlock(1). When I want to lock my screen and start xlock(1) eg. this
way 'xlock -mode
On Tue, Aug 17, 2010 at 10:19:03 +0200, LEVAI Daniel wrote:
On Tue, Aug 17, 2010 at 09:30:57 +0200, Tomas Bodzar wrote:
Hi all,
did someone saw similar problem in scrotwm(1)? Eg. when I start
xeyes(1) on empty workspace from menu M-p it simply shut down X.
Wish I hadn't tried it :) Yes,
dmesg?
On Tue, Aug 17, 2010 at 10:24:17AM +0200, Jiri B. wrote:
did someone saw similar problem in scrotwm(1)? Eg. when I start
xeyes(1) on empty workspace from menu M-p it simply shut down X. If
I start eg. xcalc(1) then everything is ok. Another problem is with
xlock(1). When I want to
I bet that is the controlled shut down where applications create windows
and then destroy them before scrotwm can focus on them. I fixed this in
cvs and would appreciate a test report. CVS instructions are on the www
scrotwm page and it conveniently installs over the pkg.
On Tue, Aug 17, 2010
On Tue, Aug 17, 2010 at 1:39 PM, Marco Peereboom sl...@peereboom.us wrote:
I bet that is the controlled shut down where applications create windows
and then destroy them before scrotwm can focus on them. B I fixed this in
cvs and would appreciate a test report. B CVS instructions are on the www
LEVAI Daniel wrote:
On Tue, Aug 17, 2010 at 09:30:57 +0200, Tomas Bodzar wrote:
Hi all,
did someone saw similar problem in scrotwm(1)? Eg. when I start
xeyes(1) on empty workspace from menu M-p it simply shut down X.
Wish I hadn't tried it :) Yes, it happens here too.
[...]
So someone
On Tue, Aug 17, 2010 at 3:30 AM, Tomas Bodzar tomas.bod...@gmail.com wrote:
did someone saw similar problem in scrotwm(1)? Eg. when I start
xeyes(1) on empty workspace from menu M-p it simply shut down X. If
I start eg. xcalc(1) then everything is ok. Another problem is with
xlock(1). When I
On Tue, 17 Aug 2010 06:40:21 -0500
Marco Peereboom sl...@peereboom.us wrote:
dmesg?
I have to first eliminate potential involvement of i/o slowdown because
of big use of softraid (i have everything except '/' on softraid).
On Tue, Aug 17, 2010 at 10:24:17AM +0200, Jiri B. wrote:
did
20 matches
Mail list logo
