From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: fzf: install fzf.vim to Neovim plugin directory
Date: Wed, 23 Sep 2020 19:17:10 +0200 [thread overview]
Message-ID: <20200923171710.yjgTWbv_b_OBXCzjMar_w0B2VeUaYxxu8brZK7FEmKA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21733@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/21733#issuecomment-697728065
Comment:
> If you're not using vim, manage the mapping manually. You can even noextract vim directories if it bothers you to have them.
Vim plugins "taking up space" isn't the issue, it's not having neovim ones.
We are already treating the vim plugin specially, by installing it manually in the template. By https://github.com/junegunn/fzf/blob/master/README-VIM.md#fzf-inside-terminal-buffer, `fzf` upstream expects the plugin to also work for neovim, so IMO it's our responsibility as packagers to ship it for all our vim alternatives.
`neovim` upstream should ideally have a way of importing plugins from vim directories, but I don't think waiting for a resolution on that should be a blocker.
next prev parent reply other threads:[~2020-09-23 17:17 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 0:41 [PR PATCH] " gbrlsnchs
2020-05-08 3:50 ` Anachron
2020-05-08 11:18 ` daniel-eys
2020-05-08 11:53 ` gbrlsnchs
2020-05-08 11:54 ` gbrlsnchs
2020-05-10 4:54 ` gbrlsnchs
2020-08-11 2:11 ` [PR PATCH] [Updated] " gbrlsnchs
2020-08-11 2:26 ` gbrlsnchs
2020-09-21 15:00 ` [PR PATCH] [Closed]: " gbrlsnchs
2020-09-21 15:08 ` [PR PATCH] [Updated] " gbrlsnchs
2020-09-21 15:43 ` ericonr
2020-09-21 15:50 ` ericonr
2020-09-21 15:51 ` ericonr
2020-09-21 15:59 ` gbrlsnchs
2020-09-21 15:59 ` gbrlsnchs
2020-09-21 16:42 ` [PR PATCH] [Updated] " gbrlsnchs
2020-09-21 16:53 ` [PR REVIEW] " ericonr
2020-09-21 16:53 ` ericonr
2020-09-21 17:27 ` [PR PATCH] [Updated] " gbrlsnchs
2020-09-21 17:30 ` [PR REVIEW] " gbrlsnchs
2020-09-21 17:31 ` gbrlsnchs
2020-09-21 17:36 ` gbrlsnchs
2020-09-21 17:36 ` gbrlsnchs
2020-09-21 18:18 ` ericonr
2020-09-21 18:59 ` gbrlsnchs
2020-09-21 19:15 ` ericonr
2020-09-21 19:24 ` [PR PATCH] [Updated] " gbrlsnchs
2020-09-21 20:02 ` gbrlsnchs
2020-09-23 16:46 ` sgn
2020-09-23 16:48 ` sgn
2020-09-23 16:48 ` sgn
2020-09-23 16:53 ` ericonr
2020-09-23 16:59 ` sgn
2020-09-23 17:12 ` ahesford
2020-09-23 17:17 ` ericonr [this message]
2020-09-23 17:20 ` gbrlsnchs
2020-09-23 17:28 ` sgn
2020-09-23 17:30 ` sgn
2020-09-23 17:34 ` gbrlsnchs
2020-09-23 17:38 ` sgn
2020-09-23 17:57 ` ericonr
2020-09-23 17:59 ` [PR PATCH] [Merged]: " ericonr
2020-09-23 20:12 ` maybe-one-day-ubermensch
2020-09-23 21:38 ` gbrlsnchs
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=20200923171710.yjgTWbv_b_OBXCzjMar_w0B2VeUaYxxu8brZK7FEmKA@z \
--to=ericonr@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).