From: Pierre Langlois <pierre.langlois@gmx.com>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: 33772@debbugs.gnu.org
Subject: bug#33772: StumpWM broken commands?
Date: Tue, 18 Dec 2018 17:34:57 +0000 [thread overview]
Message-ID: <cub4lbapwla.fsf@gmx.com> (raw)
In-Reply-To: <87k1k67uz1.fsf@dustycloud.org>
Hello!
Christopher Lemmer Webber writes:
> Ludovic Courtès writes:
>
>> Hi,
>>
>> Christopher Lemmer Webber <cwebber@dustycloud.org> skribis:
>>
>>> It seems to me that StumpWM broke somehow, for some reason. I can
>>> confirm there was a version change:
>>>
>>> -sbcl-stumpwm@18.05:out /gnu/store/i0picr2xr2aq2a52nsaw67nvar1r3khw-sbcl-stumpwm-18.05
>>> +sbcl-stumpwm@18.11:out /gnu/store/6h2iln76dx8pxdp1hsaqb1yncm8viczj-sbcl-stumpwm-18.11
>>>
>>> I am not sure if this is the cause or something else. At any rate, when
>>> I try to run commands such as "gnew" (the command to make a new
>>> group/workstation) I get back:
>>>
>>> Error In Command 'gnew': invalid number of arguments: 2
>>>
>>> I though I'd try running the command manually and check the error, but
>>> this also happens with eval! Some other commands are not affected.
>>>
>>> (I can try re-enabling the live REPL in StumpWM to play around with it,
>>> but I currently have it off because they have the same live hacking
>>> vulnerability in SBCL/SLIME that we had in Guile/Geiser some time ago.)
>>
>> Pierre, does that ring a bell?
>>
>> Others on the mailing list reported being happy with the upgrade, but
>> maybe they use different bits of StumpWM.
Ah yes, I can reproduce this :-/. Both in GuixSD and with Guix on top of
ArchLinux. The 'gnew' command does work if you pass it the name of the
new group as an argument, that's why I didn't notice this. It should
interactively ask for a name if you don't pass one so that's still a
regression.
Maybe that's a bug upstream? It would be good to try StumpWM 18.11 on
another distribution to see if this is specific to Guix. I cannot
install it on ArchLinux though at the moment.
I'll try to investigate more this week when I have more time.
Thanks!
Pierre
next prev parent reply other threads:[~2018-12-18 17:36 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 [this message]
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
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=cub4lbapwla.fsf@gmx.com \
--to=pierre.langlois@gmx.com \
--cc=33772@debbugs.gnu.org \
--cc=cwebber@dustycloud.org \
/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).