From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42980) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eS8qr-00065h-R8 for guix-patches@gnu.org; Thu, 21 Dec 2017 16:58:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eS8qo-000545-Kv for guix-patches@gnu.org; Thu, 21 Dec 2017 16:58:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:37873) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eS8qo-00053k-Cp for guix-patches@gnu.org; Thu, 21 Dec 2017 16:58:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eS8qo-0008US-5F for guix-patches@gnu.org; Thu, 21 Dec 2017 16:58:02 -0500 Subject: [bug#29569] Guile-wm +Guile-xcb patches (updates, urls,etc) Resent-Message-ID: MIME-Version: 1.0 In-Reply-To: References: <20171204231544.5usv6zwdgcxjjk2g@abyayala> <87vahimr8e.fsf@posteo.net> From: Catonano Date: Thu, 21 Dec 2017 22:57:29 +0100 Message-ID: Content-Type: multipart/alternative; boundary="089e0826969453c1210560e0c98d" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Kei Kebreau , 29569-done@debbugs.gnu.org Cc: 29569@debbugs.gnu.org --089e0826969453c1210560e0c98d Content-Type: text/plain; charset="UTF-8" ah it should be this one 2017-12-21 22:34 GMT+01:00 Catonano : > > > 2017-12-07 17:34 GMT+01:00 Kei Kebreau : > >> ng0 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 > --089e0826969453c1210560e0c98d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
ah it should be this one

2017-12-21 22:34 GMT+01:00 Catonano <ca= tonano@gmail.com>:


2017-12-07 17:34 GMT+01:00 Kei Kebreau <kkebreau@post= eo.net>:
ng0 <ng0@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<= br> > 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<= br>

--089e0826969453c1210560e0c98d--