From: Ricardo Wurmus <rekado@elephly.net>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 39311@debbugs.gnu.org
Subject: [bug#39311] [PATCH] gnu: Add guix-vim.
Date: Mon, 27 Jan 2020 23:28:20 +0100 [thread overview]
Message-ID: <87v9owttyz.fsf@elephly.net> (raw)
In-Reply-To: <20200127172032.25825-1-efraim@flashner.co.il>
Hi Efraim,
> * gnu/packages/vim.scm (guix-vim): New variable.
> ---
> gnu/packages/vim.scm | 42 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 42 insertions(+)
>
> diff --git a/gnu/packages/vim.scm b/gnu/packages/vim.scm
> index b5952e3e21..a2d715dc1c 100644
> --- a/gnu/packages/vim.scm
> +++ b/gnu/packages/vim.scm
> @@ -938,3 +938,45 @@ through its msgpack-rpc API.")
>
> (define-public python2-pynvim
> (package-with-python2 python-pynvim))
> +
> +(define-public guix-vim
Looks like we usually prefix vim extensions with “vim-”, so should this
be “vim-guix” instead…?
> + (replace 'install
> + (lambda* (#:key outputs #:allow-other-keys)
> + (let* ((out (assoc-ref outputs "out"))
> + (vimfiles (string-append out "/share/vim/vimfiles"))
> + (compiler (string-append vimfiles "/compiler"))
> + (doc (string-append vimfiles "/doc"))
> + (indent (string-append vimfiles "/indent"))
> + (ftdetect (string-append vimfiles "/ftdetect"))
> + (ftplugin (string-append vimfiles "/ftplugin"))
> + (syntax (string-append vimfiles "/syntax")))
> + (copy-recursively "compiler" compiler)
> + (copy-recursively "doc" doc)
> + (copy-recursively "indent" indent)
> + (copy-recursively "ftdetect" ftdetect)
> + (copy-recursively "ftplugin" ftplugin)
> + (copy-recursively "syntax" syntax)
> + #t))))))
The repetition here tickles me a little. How about this instead…?
(for-each (lambda (dir)
(copy-recursively dir (string-append vimfiles "/" dir)))
'("compiler" "doc" "indent" "ftdetect" "ftplugin" "syntax"))
--
Ricardo
next prev parent reply other threads:[~2020-01-27 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 17:20 [bug#39311] [PATCH] gnu: Add guix-vim Efraim Flashner
2020-01-27 22:28 ` Ricardo Wurmus [this message]
2020-01-28 7:43 ` bug#39311: " Efraim Flashner
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=87v9owttyz.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=39311@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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).