From: Efraim Flashner <efraim@flashner.co.il>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 39311-done@debbugs.gnu.org
Subject: bug#39311: [PATCH] gnu: Add guix-vim.
Date: Tue, 28 Jan 2020 09:43:17 +0200 [thread overview]
Message-ID: <20200128074317.GX1603@E5400> (raw)
In-Reply-To: <87v9owttyz.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 2337 bytes --]
On Mon, Jan 27, 2020 at 11:28:20PM +0100, Ricardo Wurmus wrote:
>
> 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…?
Good call
>
> > + (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"))
This will also be good if we ever get around to making a
vim-build-system.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-01-28 7:44 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
2020-01-28 7:43 ` Efraim Flashner [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=20200128074317.GX1603@E5400 \
--to=efraim@flashner.co.il \
--cc=39311-done@debbugs.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.
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).