From: atweiden <atweiden@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: fix(fzf): make neovim plugin optional
Date: Tue, 02 Aug 2022 23:47:40 +0200 [thread overview]
Message-ID: <20220802214740.XpY-564MlAP7j5a5ZSl3T6hPqYuocoHeEzYhNdfa4Xs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37795@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
New comment by atweiden on void-packages repository
https://github.com/void-linux/void-packages/pull/37795#issuecomment-1203246207
Comment:
> Isn't there a chance of incompatibilities between the fzf executable and the vim plugin if one uses newer command line options than are available from the executable?
Technically speaking, “yes”. But I doubt fzf’s author would release breaking changes to the fzf CLI outside of major version updates. Any devenv issues arising from this could be addressed by updating the fzf template in this repo to the newer version (or updating the devenv in question as appropriate).
As for whether a hypothetical silent majority of Vim users exist who rely on installing the fzf binary and plugin via a distro package manager for practical usage within Vim? They could continue to do so with `xbps-install vim-fzf`. I doubt if most people who barely customize Vim even use fzf within Vim, though. fzf is quite useful outside of Vim, and for that you don’t ever need the plugins.
next prev parent reply other threads:[~2022-08-02 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 20:13 [PR PATCH] " mitinarseny
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 [this message]
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=20220802214740.XpY-564MlAP7j5a5ZSl3T6hPqYuocoHeEzYhNdfa4Xs@z \
--to=atweiden@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).