From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: fix(fzf): make neovim plugin optional
Date: Sun, 17 Jul 2022 22:20:22 +0200 [thread overview]
Message-ID: <20220717202022.f810t1dexB0cIdLbo7Ux9qYId4ESjhbGVFmnOp6IT4s@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: 793 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/37795#issuecomment-1186600973
Comment:
> it can contain deprecated or even removed functionality which would cause an error while loading neovim
That one is our job as a distro to catch; and since it's using vim functionality, I find it unlikely to break either.
> For these users, it may feel a bit heavy-handed for the distro to install a {,n}vim plugin alongside any main binary (fzf in this case), when in most cases they just want the binary, and would prefer using their plugin manager to install the plugin.
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?
next prev parent reply other threads:[~2022-07-17 20:20 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 [this message]
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=20220717202022.f810t1dexB0cIdLbo7Ux9qYId4ESjhbGVFmnOp6IT4s@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).