From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 3/3] gnu: haskell-mode: Update to 16.1.
Date: Mon, 24 Oct 2016 23:38:31 +0200 [thread overview]
Message-ID: <87vawhwhpk.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPP-PHijNsx6mr0+DCyZ4SpXLKKpWQ1FrbKPWkQvqCOkZw@mail.gmail.com> (Federico Beffa's message of "Fri, 21 Oct 2016 08:29:41 +0200")
Federico Beffa <beffa@ieee.org> skribis:
> From 46bd8735643b50c9c13ebce595943ad20aa1c7f1 Mon Sep 17 00:00:00 2001
> From: Federico Beffa <beffa@fbengineering.ch>
> Date: Thu, 20 Oct 2016 20:23:11 +0200
> Subject: [PATCH 3/3] gnu: haskell-mode: Update to 16.1.
>
> * gnu/packages/emacs.scm (haskell-mode): Update to 16.1.
> [inputs]: Add 'emacs-el-search' and 'emacs-stream'.
> [propagated-inputs]: Add 'emacs-dash'.
> [arguments]: Add modules. Adapt 'pre-build' and 'install' phases.
[...]
> + (inputs
> + `(("emacs-el-search" ,emacs-el-search)
> + ("emacs-stream" ,emacs-stream)))
So these are only used at build time? Might be worth adding a comment
to make it clear why they are not propagated.
> (let ((sh (string-append (assoc-ref inputs "bash") "/bin/sh")))
> (setenv "SHELL" "sh")
> + (setenv "EMACSLOADPATH"
> + (apply string-append
> + (map (match-lambda
> + (((? (lambda (n)
> + (string-prefix? "emacs-" n)) name)
> + . dir)
> + (string-append (el-dir dir) ":"))
For readability, I’d suggest moving the lambda just below the ‘let’ and
giving it a name:
(define emacs-prefix?
(cut string-prefix "emacs-" <>))
Also, (string-concatenate …) instead of (apply string-append …).
OK with these changes, thanks!
Ludo’.
prev parent reply other threads:[~2016-10-24 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 6:29 [PATCH 3/3] gnu: haskell-mode: Update to 16.1 Federico Beffa
2016-10-24 21:38 ` Ludovic Courtès [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=87vawhwhpk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=beffa@ieee.org \
--cc=guix-devel@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 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).