From: atweiden <atweiden@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: neovim: remove alternatives.
Date: Thu, 17 Mar 2022 02:07:47 +0100 [thread overview]
Message-ID: <20220317010747.MfxyhUpbZKFaAtq3Vy5-xF7M6joe7xd--y6TXuD44UA@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: 961 bytes --]
New comment by atweiden on void-packages repository
https://github.com/void-linux/void-packages/pull/36165#issuecomment-1069799662
Comment:
Yesterday, I suggested [doing](https://github.com/void-linux/void-packages/pull/36165#issuecomment-1068754834):
```bash
# Template file for 'dash'
alternatives="
sh:sh:/usr/bin/dash
sh:sh.1:/usr/share/man/man1/dash.1"
# Template file for 'bash'
alternatives="
sh:sh:/usr/bin/bash
sh:sh.1:/usr/share/man/man1/bash.1"
# Template file for 'neovim'
alternatives="
vi:vi:/usr/bin/nvim
vi:vi.1:/usr/share/man/man1/nvim.1
```
I’ve updated the PR accordingly, to minimize any confusion.
I simply don’t recognize any level of logical consistency in the way Neovim is allowed to easily override `vim` on Void systems. There is no logical difference between allowing this and allowing `bash` to override `dash`. It’s simply not what most users want or expect, edge cases from Debian aside.
next prev parent reply other threads:[~2022-03-17 1:07 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
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 [this message]
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=20220317010747.MfxyhUpbZKFaAtq3Vy5-xF7M6joe7xd--y6TXuD44UA@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).