From: mitinarseny <mitinarseny@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] fix(fzf): make neovim plugin optional
Date: Fri, 01 Jul 2022 22:13:14 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37795@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
There is a new pull request by mitinarseny against master on the void-packages repository
https://github.com/mitinarseny/void-packages patch-2
https://github.com/void-linux/void-packages/pull/37795
fix(fzf): make neovim plugin optional
#### Testing the changes
- I tested the changes in this PR: **NO**
Motivation: `fzf` package installs `fzf.vim` in `/usr/share/nvim/runtime/plugin/`, but not all people who use fzf, want to use it inside nvim, so it should be placed in `/usr/share/nvim/runtime/pack/fzf/opt/` to make it optional. Users can load this plugin in their `init.vim`:
```vim
packadd fzf
```
A patch file from https://github.com/void-linux/void-packages/pull/37795.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-2-37795.patch --]
[-- Type: text/x-diff, Size: 837 bytes --]
From d183a8c42da2a975292ee5754675bf60d19c2b1e Mon Sep 17 00:00:00 2001
From: Arseny Mitin <mitinarseny@gmail.com>
Date: Fri, 1 Jul 2022 23:08:54 +0300
Subject: [PATCH] fix(fzf): make neovim plugin optional
---
srcpkgs/fzf/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/fzf/template b/srcpkgs/fzf/template
index 86789e858d66..e4a9ea96189e 100644
--- a/srcpkgs/fzf/template
+++ b/srcpkgs/fzf/template
@@ -21,7 +21,7 @@ post_install() {
sed -i -e 's#source ~/\.fzf\.bash; ##' shell/key-bindings.bash
vinstall plugin/fzf.vim 644 usr/share/vim/vimfiles/plugin
- vinstall plugin/fzf.vim 644 usr/share/nvim/runtime/plugin
+ vinstall plugin/fzf.vim 644 usr/share/nvim/runtime/pack/fzf/opt/plugin
vinstall shell/completion.bash 644 usr/share/fzf
vinstall shell/completion.zsh 644 usr/share/fzf
next reply other threads:[~2022-07-01 20:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 20:13 mitinarseny [this message]
2022-07-02 0:51 ` sgn
2022-07-02 0:53 ` sgn
2022-07-05 14:15 ` ericonr
2022-07-06 0:00 ` sgn
2022-07-06 22:39 ` atweiden
2022-07-07 9:36 ` mitinarseny
2022-07-09 22:55 ` atweiden
2022-07-17 20:20 ` ericonr
2022-08-02 21:47 ` atweiden
2022-11-01 2:14 ` github-actions
2022-11-16 2:11 ` [PR PATCH] [Closed]: " github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37795@inbox.vuxu.org \
--to=mitinarseny@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).