From: atweiden <atweiden@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Neovim template should not contest Vim namespace in `alternatives`
Date: Sun, 27 Mar 2022 22:10:36 +0200 [thread overview]
Message-ID: <20220327201036.Fl_B9aBygx5EOQ5ApNwMdjkXt7xyxfFJaeqsfCOPgGU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36164@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
New comment by atweiden on void-packages repository
https://github.com/void-linux/void-packages/issues/36164#issuecomment-1080009878
Comment:
Thanks for opining, @Vaelatern.
I noticed your name is listed as [the maintainer of Neomutt](https://github.com/void-linux/void-packages/blob/a62f4724bb2f99f9ca8e1a66e8eee76bd3ffd1ce/srcpkgs/neomutt/template#L19).
According to Neomutt’s homepage:
> NeoMutt is a command line mail reader (or MUA). **It’s a fork of Mutt with added features**.
This seems quite analagous to the relationship between Neovim and Vim.
However, the Neomutt template doesn’t use `alternatives` at all.
Why is `mutt` protected from `neomutt` symlinks, while `vim` isn’t protected from `nvim`?
Bear in mind I’ve [proposed](https://github.com/void-linux/void-packages/pull/36165) continuing to allow `nvim` to symlink `vi` — so users who don’t care about the gulf between Vim and Neovim can still blindly install one over the other and just type `vi` to maintain the same workflow.
next prev parent reply other threads:[~2022-03-27 20:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 22:03 [ISSUE] " atweiden
2022-03-15 22:36 ` classabbyamp
2022-03-15 22:39 ` classabbyamp
2022-03-15 22:44 ` classabbyamp
2022-03-15 22:45 ` classabbyamp
2022-03-15 22:47 ` classabbyamp
2022-03-15 23:35 ` atweiden
2022-03-16 0:03 ` paper42
2022-03-16 1:39 ` atweiden
2022-03-16 2:27 ` classabbyamp
2022-03-16 2:28 ` classabbyamp
2022-03-16 2:31 ` Duncaen
2022-03-16 2:39 ` Duncaen
2022-03-16 5:18 ` atweiden
2022-03-16 6:00 ` atweiden
2022-03-16 9:21 ` paper42
2022-03-16 9:51 ` atweiden
2022-03-16 21:55 ` lemmi
2022-03-17 0:35 ` atweiden
2022-03-17 0:52 ` atweiden
2022-03-17 0:54 ` Duncaen
2022-03-17 0:58 ` Duncaen
2022-03-17 1:07 ` atweiden
2022-03-17 1:09 ` tibequadorian
2022-03-17 1:10 ` [ISSUE] [CLOSED] " Duncaen
2022-03-17 1:12 ` tibequadorian
2022-03-17 1:14 ` Duncaen
2022-03-17 1:35 ` Duncaen
2022-03-17 1:50 ` atweiden
2022-03-18 12:09 ` tibequadorian
2022-03-18 12:09 ` tibequadorian
2022-03-18 12:09 ` tibequadorian
2022-03-18 12:12 ` tibequadorian
2022-03-27 18:28 ` Vaelatern
2022-03-27 20:10 ` atweiden [this message]
2022-03-27 20:30 ` classabbyamp
2022-03-27 22:00 ` Vaelatern
2022-03-27 22:49 ` atweiden
2022-03-28 1:15 ` Vaelatern
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=20220327201036.Fl_B9aBygx5EOQ5ApNwMdjkXt7xyxfFJaeqsfCOPgGU@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).