From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: neovim: remove alternatives.
Date: Wed, 16 Mar 2022 07:34:45 +0100 [thread overview]
Message-ID: <20220316063445.89RPW5FV_yx9Wu3khOwKqTMrr2OOSdO0XwFVoOUOcPk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36165@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/36165#issuecomment-1068782911
Comment:
Making dash bash breaks all scripts with bash shebang, installing nvim before vim makes it the default provider for the vim alternative group which you can easily fix with xbps-alternatives, avoid by installing vim first (instead of alphabetically sorting xbps-install arguments or by just not installing nvim. It also doesn't break half the system, all it does is make the cursor werid on your system.
There would be no point in alternatives, if the requirement would be that they are 100% compatible, some things have stricter requirements than others, like shells, while other more interactive programs don't.
next prev parent reply other threads:[~2022-03-16 6:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 22:15 [PR PATCH] " atweiden
2022-03-16 5:44 ` atweiden
2022-03-16 6:29 ` Duncaen
2022-03-16 6:33 ` Duncaen
2022-03-16 6:34 ` Duncaen [this message]
2022-03-16 8:50 ` atweiden
2022-03-16 9:19 ` paper42
2022-03-17 1:05 ` [PR PATCH] [Updated] " atweiden
2022-03-17 1:07 ` atweiden
2022-03-17 1:07 ` atweiden
2022-03-17 1:11 ` [PR PATCH] [Closed]: " Duncaen
2022-03-27 18:28 ` [RFC] " Vaelatern
2022-03-27 20:35 ` paper42
2022-03-27 20:35 ` [PR PATCH] [Closed]: " paper42
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=20220316063445.89RPW5FV_yx9Wu3khOwKqTMrr2OOSdO0XwFVoOUOcPk@z \
--to=duncaen@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).