git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>,
	"'Felipe Contreras'" <felipe.contreras@gmail.com>
Cc: "'brian m. carlson'" <sandals@crustytoothpaste.net>,
	"'Git'" <git@vger.kernel.org>, "'Jeff King'" <peff@peff.net>,
	"'Emily Shaffer'" <emilyshaffer@google.com>
Subject: RE: [PATCH] Add project-wide .vimrc configuration
Date: Wed, 9 Dec 2020 11:18:31 -0500	[thread overview]
Message-ID: <01a801d6ce46$f2cad520$d8607f60$@nexbridge.com> (raw)
In-Reply-To: <xmqqh7ov2y97.fsf@gitster.c.googlers.com>

On December 9, 2020 3:13 AM, Junio C Hamano wrote:
> To: Felipe Contreras <felipe.contreras@gmail.com>
> Cc: brian m. carlson <sandals@crustytoothpaste.net>; Git
> <git@vger.kernel.org>; Jeff King <peff@peff.net>; Emily Shaffer
> <emilyshaffer@google.com>
> Subject: Re: [PATCH] Add project-wide .vimrc configuration
> 
> Felipe Contreras <felipe.contreras@gmail.com> writes:
> 
> >> *2* In other words, I doubt these graphs are depicting "how widely is
> >> an editor used by developers".  It is just showing how often it is
> >> installed, and I know the primary workstation I use daily has vim and
> >> nano installed without me choosing to have them, as opposed to emacs
> >> I had to manually install, and I only use vim once every month and
> >> nano once every quarter.
> >
> > Yes, but in Arch Linux at least no editor is installed by default.
> 
> I thought everybody has nano not because it is adequate and usable for
> them, but because it comes by default with distros, and distro in turn
choose
> nano not because it is particularly popular but is small enough not to
matter
> if left behind unused when the user chooses a real editor.
> 
> But you are essentially usaying that 80% of Arch users install nano by
choice.
> I find it doubly surprising.

I know of perhaps 3 or 4 nano users in the NonStop community. There are
probably three orders of magnitude more vi/vim users. vim and vi both come
installed on the platform by default. Nano is an add-on that my team builds
as a courtesy but there's small interest but it is loyal.

Regards,
Randall


      parent reply	other threads:[~2020-12-09 16:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09  0:26 [PATCH] Add project-wide .vimrc configuration Felipe Contreras
2020-12-09  1:08 ` Junio C Hamano
2020-12-09  2:32   ` Felipe Contreras
2020-12-09  1:18 ` Aaron Schrab
2020-12-09  3:15   ` Junio C Hamano
2020-12-09  6:28   ` Felipe Contreras
2020-12-09  1:32 ` Denton Liu
2020-12-09  6:20   ` Felipe Contreras
2020-12-09  2:23 ` brian m. carlson
2020-12-09  6:36   ` Felipe Contreras
2020-12-09  6:54     ` Junio C Hamano
2020-12-09  7:16       ` Felipe Contreras
2020-12-09  8:13         ` Junio C Hamano
2020-12-09  8:52           ` Felipe Contreras
2020-12-09 16:18           ` Randall S. Becker [this message]

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='01a801d6ce46$f2cad520$d8607f60$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=emilyshaffer@google.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=sandals@crustytoothpaste.net \
    /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).