unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "N. Y." <ningyuan.sg@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Meaning of symbol prefixed with "#$"
Date: Sat, 27 May 2023 23:31:16 +0000	[thread overview]
Message-ID: <CAEavL=Xmm1p-iMkK2D1NW5bGHt2aQtW06_4_ZsrTqzN0osvRSA@mail.gmail.com> (raw)
In-Reply-To: <87ilcex5ra.fsf@elephly.net>

Thanks so much for your suggestion! Can I ask for a name for these
notations, #~ and #$? I would like to learn more about them, but they are
difficult to Google for.

On Fri, May 26, 2023 at 7:17 PM Ricardo Wurmus <rekado@elephly.net> wrote:

>
> (Moving this to help-guix instead of guile-user.)
>
> "N. Y." <ningyuan.sg@gmail.com> writes:
>
> > (arguments
> >   '(#:phases (modify-phases %standard-phases
> >     (add-after 'unpack 'amend-version
> >       (lambda _
> >         (substitute* "setup.py"
> >           (("versioneer.get_version\\(\\)")
> >           (string-append "\"" #$version "\"")))))
>
> You can only use #$ inside an expression starting with #~.  This should
> work:
>
> --8<---------------cut here---------------start------------->8---
> (arguments
>   (list
>     #:phases
>     #~(modify-phases %standard-phases
>        (add-after 'unpack 'amend-version
>          (lambda _
>            (substitute* "setup.py"
>              (("versioneer.get_version\\(\\)")
>              (string-append "\"" #$version "\""))))))))
> --8<---------------cut here---------------end--------------->8---
>
> --
> Ricardo
>

  reply	other threads:[~2023-05-29 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEavL=UnjHtxpWmjE0sxMFV7QFYoRdNdov6=N-sfUKxfbeX3bg@mail.gmail.com>
2023-05-26 19:14 ` Meaning of symbol prefixed with "#$" Ricardo Wurmus
2023-05-27 23:31   ` N. Y. [this message]
2023-05-28  7:28     ` Ricardo Wurmus
2023-05-29  8:40       ` N. Y.

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='CAEavL=Xmm1p-iMkK2D1NW5bGHt2aQtW06_4_ZsrTqzN0osvRSA@mail.gmail.com' \
    --to=ningyuan.sg@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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.
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).