From: Jean-Pierre De Jesus DIAZ via Guix-patches via <guix-patches@gnu.org>
To: 68060@debbugs.gnu.org
Cc: Jean-Pierre De Jesus DIAZ <jean@foundationdevices.com>
Subject: [bug#68060] [PATCH 3/5] gnu: vim-coqtail: Move vim-full to arguments.
Date: Wed, 27 Dec 2023 16:31:48 +0100 [thread overview]
Message-ID: <724bdaab2e29ea106be52177620cd2c5d53d203d.1703690765.git.jean@foundationdevices.com> (raw)
In-Reply-To: <cover.1703690765.git.jean@foundationdevices.com>
* gnu/packages/vim.scm (vim-coqtail): Move vim-full from native-inputs
to arguments.
Change-Id: I20cc1e0772727f8fc7db70b42151432fb6349fc7
---
gnu/packages/vim.scm | 14 ++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/gnu/packages/vim.scm b/gnu/packages/vim.scm
index 7fc6cae6e9..e27feb13f7 100644
--- a/gnu/packages/vim.scm
+++ b/gnu/packages/vim.scm
@@ -470,7 +470,8 @@ (define-public vim-coqtail
"0av2m075n6z05ah9ndrgnp9s16yrz6n2lj0igd9fh3c5k41x5xks"))))
(build-system vim-build-system)
(arguments
- '(#:plugin-name "coqtail"
+ `(#:plugin-name "coqtail"
+ #:vim ,vim-full ; Plugin needs Python 3.
#:phases
(modify-phases %standard-phases
(add-before 'install 'check
@@ -491,9 +492,7 @@ (define-public vim-coqtail
"/share/vim/vimfiles/pack/guix/start/vader")))
(with-directory-excursion "tests/vim"
(setenv "VADER_PATH" vader-path)
- (invoke (string-append
- (assoc-ref (or native-inputs inputs) "vim-full")
- "/bin/vim")
+ (invoke "vim"
"-E" "-Nu" "vimrc"
"-c" "Vader! *.vader")))
@@ -501,10 +500,9 @@ (define-public vim-coqtail
;; they don't get installed.
(delete-file-recursively "python/__pycache__")))))))
(native-inputs
- `(("coq-for-coqtail" ,coq-for-coqtail)
- ("python-pytest" ,python-pytest)
- ("vim-full" ,vim-full) ; Plugin needs Python 3.
- ("vim-vader" ,vim-vader)))
+ (list coq-for-coqtail
+ python-pytest
+ vim-vader))
(propagated-inputs (list coq coq-ide-server))
(synopsis "Interactive Coq proofs in Vim")
(description "Coqtail enables interactive Coq proof development in Vim
--
2.41.0
next prev parent reply other threads:[~2023-12-27 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 15:28 [bug#68060] [PATCH 0/5] gnu: Add neovim-coqtail Jean-Pierre De Jesus DIAZ via Guix-patches via
2023-12-27 15:31 ` [bug#68060] [PATCH 1/5] gnu: vim-vader: Allow using neovim for tests Jean-Pierre De Jesus DIAZ via Guix-patches via
2023-12-27 15:31 ` [bug#68060] [PATCH 2/5] gnu: Add neovim-vader Jean-Pierre De Jesus DIAZ via Guix-patches via
2023-12-27 15:31 ` Jean-Pierre De Jesus DIAZ via Guix-patches via [this message]
2023-12-27 15:31 ` [bug#68060] [PATCH 4/5] gnu: vim-coqtail: Allow using neovim for tests Jean-Pierre De Jesus DIAZ via Guix-patches via
2023-12-27 15:31 ` [bug#68060] [PATCH 5/5] gnu: Add neovim-coqtail Jean-Pierre De Jesus DIAZ via Guix-patches via
2024-01-01 9:00 ` bug#68060: [PATCH 0/5] " 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=724bdaab2e29ea106be52177620cd2c5d53d203d.1703690765.git.jean@foundationdevices.com \
--to=guix-patches@gnu.org \
--cc=68060@debbugs.gnu.org \
--cc=jean@foundationdevices.com \
/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).