From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: 33772@debbugs.gnu.org
Subject: bug#33772: StumpWM broken commands?
Date: Sun, 16 Dec 2018 14:05:46 -0500 [thread overview]
Message-ID: <878t0pqol1.fsf@dustycloud.org> (raw)
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.)
next reply other threads:[~2018-12-16 19:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 19:05 Christopher Lemmer Webber [this message]
2018-12-18 11:18 ` bug#33772: StumpWM broken commands? 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878t0pqol1.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=33772@debbugs.gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.