GNU bug report logs - #29569
Guile-wm +Guile-xcb patches (updates, urls,etc)

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 29569 in the body.
You can then email your comments to 29569 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: ng0 <ng0 <at> n0.is>
To: guix-patches <at> gnu.org
Subject: Guile-wm +Guile-xcb patches (updates, urls,etc)
Date: Mon, 4 Dec 2017 23:15:44 +0000

[Message part 1 (text/plain, inline)]

So,

I've updated to the latest commits in the hope that it would
fix the problem I have where guile-wm keeps crashing.

It's my first couple of hours with guile-wm and I don't know
the code yet, so I'll look into it why none of the recent commits
fixed it (while the messages said they should).

The state of it is as before. I doubt Guile-wm is stable as it
is in our master.
There are some changes. Like upstream made building with
Guile 2.2 an option, the original home page is gone, development
happens on github, etc.
I've made the change to use 2.2 a commit on its own.
I'll contribute a fix to upstream as soon as I can which will
address the fact that their build system picks 2.2 even when 2.0
is given. This should not happen.

Nice project, with some more work it could replace scrotwm for me.

Rntime crashes (like we have them now) would be good to get
automated tests for these, simulating garbage keystrokes etc.
Long store short, here are 5 patches and I'll contact the
upstream developer soon.
-- 
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
  WWW: https://n0.is

[0001-gnu-guile-xcb-Update-to-1.3-1.db7d5a3.patch (text/plain, attachment)]

[0002-gnu-guile-wm-Update-to-1.0-1.f3c7b3b.patch (text/plain, attachment)]

[0003-gnu-guile-wm-and-guile-xcb-Build-with-guile-2.2.patch (text/plain, attachment)]

[0004-gnu-guile-xcb-Fix-up-indentation.patch (text/plain, attachment)]

[0005-gnu-guile-wm-Fix-up-indentation.patch (text/plain, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #8 received at 29569 <at> debbugs.gnu.org (full text, mbox):

From: Kei Kebreau <kkebreau <at> posteo.net>
To: ng0 <ng0 <at> n0.is>
Cc: 29569 <at> debbugs.gnu.org
Subject: Re: [bug#29569] Guile-wm +Guile-xcb patches (updates, urls,etc)
Date: Thu, 07 Dec 2017 11:34:41 -0500

[Message part 1 (text/plain, inline)]

ng0 <ng0 <at> n0.is> writes:

> So,
>
> I've updated to the latest commits in the hope that it would
> fix the problem I have where guile-wm keeps crashing.
>
> It's my first couple of hours with guile-wm and I don't know
> the code yet, so I'll look into it why none of the recent commits
> fixed it (while the messages said they should).
>
> The state of it is as before. I doubt Guile-wm is stable as it
> is in our master.
> There are some changes. Like upstream made building with
> Guile 2.2 an option, the original home page is gone, development
> happens on github, etc.
> I've made the change to use 2.2 a commit on its own.
> I'll contribute a fix to upstream as soon as I can which will
> address the fact that their build system picks 2.2 even when 2.0
> is given. This should not happen.
>
> Nice project, with some more work it could replace scrotwm for me.
>
> Rntime crashes (like we have them now) would be good to get
> automated tests for these, simulating garbage keystrokes etc.
> Long store short, here are 5 patches and I'll contact the
> upstream developer soon.

LGTM! Pushed to master.

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 29569 <at> debbugs.gnu.org (full text, mbox):

From: Catonano <catonano <at> gmail.com>
To: Kei Kebreau <kkebreau <at> posteo.net>
Cc: 29569 <at> debbugs.gnu.org, ng0 <ng0 <at> n0.is>
Subject: Re: [bug#29569] Guile-wm +Guile-xcb patches (updates, urls,etc)
Date: Thu, 21 Dec 2017 22:34:30 +0100

[Message part 1 (text/plain, inline)]

2017-12-07 17:34 GMT+01:00 Kei Kebreau <kkebreau <at> posteo.net>:

> ng0 <ng0 <at> n0.is> writes:
>
> > So,
> >
> > I've updated to the latest commits in the hope that it would
> > fix the problem I have where guile-wm keeps crashing.
> >
> > It's my first couple of hours with guile-wm and I don't know
> > the code yet, so I'll look into it why none of the recent commits
> > fixed it (while the messages said they should).
> >
> > The state of it is as before. I doubt Guile-wm is stable as it
> > is in our master.
> > There are some changes. Like upstream made building with
> > Guile 2.2 an option, the original home page is gone, development
> > happens on github, etc.
> > I've made the change to use 2.2 a commit on its own.
> > I'll contribute a fix to upstream as soon as I can which will
> > address the fact that their build system picks 2.2 even when 2.0
> > is given. This should not happen.
> >
> > Nice project, with some more work it could replace scrotwm for me.
> >
> > Rntime crashes (like we have them now) would be good to get
> > automated tests for these, simulating garbage keystrokes etc.
> > Long store short, here are 5 patches and I'll contact the
> > upstream developer soon.
>
> LGTM! Pushed to master.
>


ehm, this bug could be closed, then ?

I'd do it myself but I can't remember how to send control messages

[Message part 2 (text/html, inline)]

Message #16 received at 29569 <at> debbugs.gnu.org (full text, mbox):

From: Catonano <catonano <at> gmail.com>
To: Kei Kebreau <kkebreau <at> posteo.net>, 29569-done <at> debbugs.gnu.org
Cc: 29569 <at> debbugs.gnu.org, ng0 <ng0 <at> n0.is>
Subject: Re: [bug#29569] Guile-wm +Guile-xcb patches (updates, urls,etc)
Date: Thu, 21 Dec 2017 22:57:29 +0100

[Message part 1 (text/plain, inline)]

ah it should be this one

2017-12-21 22:34 GMT+01:00 Catonano <catonano <at> gmail.com>:

>
>
> 2017-12-07 17:34 GMT+01:00 Kei Kebreau <kkebreau <at> posteo.net>:
>
>> ng0 <ng0 <at> n0.is> writes:
>>
>> > So,
>> >
>> > I've updated to the latest commits in the hope that it would
>> > fix the problem I have where guile-wm keeps crashing.
>> >
>> > It's my first couple of hours with guile-wm and I don't know
>> > the code yet, so I'll look into it why none of the recent commits
>> > fixed it (while the messages said they should).
>> >
>> > The state of it is as before. I doubt Guile-wm is stable as it
>> > is in our master.
>> > There are some changes. Like upstream made building with
>> > Guile 2.2 an option, the original home page is gone, development
>> > happens on github, etc.
>> > I've made the change to use 2.2 a commit on its own.
>> > I'll contribute a fix to upstream as soon as I can which will
>> > address the fact that their build system picks 2.2 even when 2.0
>> > is given. This should not happen.
>> >
>> > Nice project, with some more work it could replace scrotwm for me.
>> >
>> > Rntime crashes (like we have them now) would be good to get
>> > automated tests for these, simulating garbage keystrokes etc.
>> > Long store short, here are 5 patches and I'll contact the
>> > upstream developer soon.
>>
>> LGTM! Pushed to master.
>>
>
>
> ehm, this bug could be closed, then ?
>
> I'd do it myself but I can't remember how to send control messages
>

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.