All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.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 02:52:57 -0600	[thread overview]
Message-ID: <CAMP44s1vJj6QJjS8ApM_wiVunPo6093_4M-ghJB_PTqZhnmm0A@mail.gmail.com> (raw)
In-Reply-To: <xmqqh7ov2y97.fsf@gitster.c.googlers.com>

On Wed, Dec 9, 2020 at 2:13 AM Junio C Hamano <gitster@pobox.com> wrote:
>
> 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 double checked. The installation instructions [1] do tell you to
pick an editor, and they don't suggest any.

I am half-surprised. The StackOverflow question "How do I exit the Vim
editor?" has 2.2 million views [2], there's countless memes about that
ordeal [3], and the SO team even found it wise to write a blog post
about it [4]. I don't know how to exit emacs (Ctrl-X Ctrl-e?), and I
suspect many emacs users don't know how to exit vim.

Nano doesn't have this problem. Which means for somebody entering the
world of Linux, that's a plus.

Cheers.

[1] https://wiki.archlinux.org/index.php/Installation_guide#Install_essential_packages
[2] https://stackoverflow.com/questions/11828270/how-do-i-exit-the-vim-editor
[3] https://twitter.com/iamdevloper/status/993821761648103425
[4] https://stackoverflow.blog/2017/05/23/stack-overflow-helping-one-million-developers-exit-vim/


--
Felipe Contreras

  reply	other threads:[~2020-12-09  8:53 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 [this message]
2020-12-09 16:18           ` Randall S. Becker

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=CAMP44s1vJj6QJjS8ApM_wiVunPo6093_4M-ghJB_PTqZhnmm0A@mail.gmail.com \
    --to=felipe.contreras@gmail.com \
    --cc=emilyshaffer@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.