From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: 33772@debbugs.gnu.org, Alex Kost <alezost@gmail.com>
Subject: bug#33772: StumpWM broken commands?
Date: Wed, 19 Dec 2018 09:49:25 -0500 [thread overview]
Message-ID: <87sgyty3ka.fsf@dustycloud.org> (raw)
In-Reply-To: <87d0px7hv8.fsf@dustycloud.org>
Christopher Lemmer Webber writes:
> Pierre Langlois writes:
>
>> Alex Kost writes:
>>
>>> I have built stumpwm from the latest commit (which is one commit after
>>> 18.11 release) and tried it on GuixSD and on ArchLinux. Works for me
>>> on both systems, so it's probably not an upstream bug.
>>
>> Hi Alex,
>>
>> I was investigating just now and thought I'd try that one commit that
>> was pushed after the release. The description doesn't sound like it
>> would fix the problem but it was easy to try that. But it looks like it
>> does fix the problem!
>>
>> Can you confirm the attached patch works for you?
>>
> I haven't tried it yet but it makes a lot of sense that this would fix
> it. Both gnew and eval interactively pull up a request for a line of
> input.
I applied your patch to my machine and it fixed it... thank you! I
pushed the patch upstream to guix master.
next prev parent reply other threads:[~2018-12-19 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 19:05 bug#33772: StumpWM broken commands? Christopher Lemmer Webber
2018-12-18 11:18 ` Ludovic Courtès
2018-12-18 14:47 ` Christopher Lemmer Webber
2018-12-18 17:34 ` Pierre Langlois
2018-12-18 18:57 ` Christopher Lemmer Webber
2018-12-19 10:37 ` Ludovic Courtès
2018-12-18 21:23 ` Alex Kost
2018-12-18 21:29 ` Pierre Langlois
2018-12-19 13:42 ` Christopher Lemmer Webber
2018-12-19 14:49 ` Christopher Lemmer Webber [this message]
2018-12-19 14:56 ` Pierre Langlois
2019-12-24 1:58 ` Brett Gilio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgyty3ka.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=33772@debbugs.gnu.org \
--cc=alezost@gmail.com \
--cc=pierre.langlois@gmx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).