all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Simon Josefsson via Guix-patches via <guix-patches@gnu.org>
Cc: Simon Josefsson <simon@josefsson.org>,
	ludo@gnu.org, 60369-done@debbugs.gnu.org
Subject: bug#60369: [PATCH v3] gnu: Add eweouz.
Date: Mon, 08 May 2023 19:24:20 +0200	[thread overview]
Message-ID: <874jomybwb.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87r0rvjg6h.fsf_-_@josefsson.org> (Simon Josefsson via Guix-patches via's message of "Fri, 05 May 2023 11:11:50 +0200")

Hello,

Simon Josefsson via Guix-patches via <guix-patches@gnu.org> writes:
> Subject: [PATCH v3] gnu: Add eweouz.
>
> * gnu/packages/emacs-xyz.scm (eweouz): New variable.

Changed name to emacs-ewouz in the commit message and applied your
patch. Thank you.

> +            (lambda* (#:key outputs #:allow-other-keys)
> +              (emacs-substitute-sexps "eweouz.el"
> +                ("eweouz-helper-dirs"
> +                 `(list ,(string-append (assoc-ref outputs "out")
> +                                        "/libexec/eweouz"))))))

Here, I used (lambda _ ...) and #$output instead of (assoc-ref …)

Regards,
-- 
Nicolas Goaziou




  reply	other threads:[~2023-05-08 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27 22:47 [bug#60369] [PATCH] gnu: Add eweouz Simon Josefsson via Guix-patches via
2023-01-31 22:42 ` Ludovic Courtès
2023-02-05 17:08   ` [bug#60369] [PATCH v2] " Simon Josefsson via Guix-patches via
2023-04-28  8:35     ` Simon Josefsson via Guix-patches via
2023-05-03 12:59     ` Nicolas Goaziou
2023-05-05  9:11       ` [bug#60369] [PATCH v3] " Simon Josefsson via Guix-patches via
2023-05-08 17:24         ` Nicolas Goaziou [this message]
2023-05-09  7:21           ` Simon Josefsson via Guix-patches via

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=874jomybwb.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=60369-done@debbugs.gnu.org \
    --cc=guix-patches@gnu.org \
    --cc=ludo@gnu.org \
    --cc=simon@josefsson.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.