From: ofiala-a51 <ofiala-a51@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] base-system: add nano to dependencies.
Date: Fri, 30 Oct 2020 23:48:24 +0100 [thread overview]
Message-ID: <20201030224824.08AciuU9-1cgIuI2eSkY0OTG9B6F1YREumpVIC9pBE4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25120@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
New comment by ofiala-a51 on void-packages repository
https://github.com/void-linux/void-packages/pull/25120#issuecomment-719832744
Comment:
I personally think using arguments like "`nano` is easier to use and way simpler **for someone who isn't used to command line stuff**" (additional highlighting done by me) for additions to base-system is not a direction that Void should take. There are already many other Linux distributions that are optimized for people who aren't used to command line stuff. Compared with many of the things new Void user has to deal with in order to get a fully functional system, `:wq` seems completely minor to me, and definitely doesn't justify this addition. Users who are not comfortable with vi can install nano the second their system is able to connect to the repos.
next prev parent reply other threads:[~2020-10-30 22:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 18:37 [PR PATCH] " ericonr
2020-09-26 18:43 ` hippi777
2020-09-26 19:02 ` hippi777
2020-09-26 19:18 ` mobinmob
2020-09-26 19:21 ` mobinmob
2020-09-26 19:42 ` Anachron
2020-09-26 20:05 ` mobinmob
2020-09-26 20:24 ` ericonr
2020-09-26 20:24 ` ericonr
2020-09-26 20:30 ` hippi777
2020-09-26 22:49 ` q66
2020-09-26 22:50 ` q66
2020-10-30 22:46 ` ofiala-a51
2020-10-30 22:48 ` ofiala-a51 [this message]
2020-10-30 22:48 ` ofiala-a51
2020-10-30 23:04 ` pullmoll
2020-10-31 15:41 ` ericonr
2020-12-30 7:09 ` the-maldridge
2021-02-03 4:56 ` ericonr
2021-02-03 4:56 ` [PR PATCH] [Closed]: " ericonr
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=20201030224824.08AciuU9-1cgIuI2eSkY0OTG9B6F1YREumpVIC9pBE4@z \
--to=ofiala-a51@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).