unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Trev <trev@trevdev.ca>
To: Maxime Devos <maximedevos@telenet.be>, 57757@debbugs.gnu.org
Subject: [bug#57757] [PATCH] gnu: Add sbcl-stumpwm-pamixer
Date: Thu, 22 Sep 2022 13:35:14 -0700	[thread overview]
Message-ID: <87mtar6tbx.fsf@codinator.mail-host-address-is-not-set> (raw)
In-Reply-To: <3ed10c4a-a3b8-3303-cc79-fbc1f9a90e41@telenet.be>

[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]

Maxime Devos <maximedevos@telenet.be> writes:

> On 19-09-2022 23:34, Trev wrote:
>>> (arguments
>>>     (list #:asd-systems ''(:pa-mixers)
>>>           #:phases
>>>           #~(modify-phases [...])))
>>>
>>> (i.e., you are removing a layer of quoting by turning the quasiquote
>>> into a quote, so it needs to be readded for the #:asd-systems).
>>>
>> I see a double-quote there with ~''(:pamixer)~ - which is not something
>> I have ever tried to do before.  Is this a typo?
>
> No, it's intentional -- if you do '(:pa-mixers), the code (:pa-mixers) 
> is passed to the builder, but that can't work, as :pa-mixers is 
> undefined (or a keyword, depending on how the Guile reader is 
> configured).  If you do ''(:pa-mixers), the code '(:pa-mixers) is passed 
> to the builder, as intended.
>
> If you change ''(:pa-mixers) to '(pa-mixers), then I expect you'll get a 
> build failure.
>

I feel a little silly because after I asked my question I went ahead and
ran a ripgrep on the project root for a pattern of ''( and found
numerous occurences of it.  Of course it failed without the double
quote.

Thanks for all of your helpful feedback.  I have made notes so that I
can recall these concepts later.

-- 

Trev : 0FB7 D06B 4A2A F07E AD5B  1169 183B 6306 8AA1 D206

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

      reply	other threads:[~2022-09-22 20:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 21:41 [bug#57757] [PATCH] * gnu/packages/wm.scm: Add sbcl-stumpwm-pamixer Trevor Richards
2022-09-12 21:41 ` [bug#57757] [PATCH] gnu: " Trevor Richards
2022-09-16  7:50   ` Guillaume Le Vaillant
2022-09-12 21:41 ` Trevor Richards
2022-09-16  9:07 ` [bug#57757] [PATCH] * gnu/packages/wm.scm: " Maxime Devos
2022-09-19 14:31   ` Trev
2022-09-19 16:17     ` Maxime Devos
2022-09-19 17:29       ` Trev
2022-09-19 17:47 ` [bug#57757] [PATCH] gnu: " Trevor Richards
2022-09-19 18:05   ` Maxime Devos
2022-09-19 18:22     ` Trev
2022-09-19 18:33       ` Maxime Devos
2022-09-19 21:34         ` Trev
2022-09-20  4:38           ` Trevor Richards
2022-09-20  7:17             ` bug#57757: " Guillaume Le Vaillant
2022-09-22 19:08           ` [bug#57757] " Maxime Devos
2022-09-22 20:35             ` Trev [this message]

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=87mtar6tbx.fsf@codinator.mail-host-address-is-not-set \
    --to=trev@trevdev.ca \
    --cc=57757@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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).