From: Junio C Hamano <gitster@pobox.com>
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
Date: Tue, 08 Dec 2020 22:54:58 -0800 [thread overview]
Message-ID: <xmqqlfe731vh.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CAMP44s0W3En0ZuNfBOOZhfeFUeFRvEFs7khAFRraocuDaFpbNA@mail.gmail.com> (Felipe Contreras's message of "Wed, 9 Dec 2020 00:36:16 -0600")
Felipe Contreras <felipe.contreras@gmail.com> writes:
>> We have an .editorconfig file[0], which is a cross-editor file that can be
>> used to specify these settings. It is supported by many editors out of
> ...
> Also, we don't have to support configurations for every editor under
> the sun, that's a slippery slope fallacy.
>
> We can stop at 1 editor: the most widely used editor by developers by far [1].
>
> Cheers.
>
> [1] https://pkgstats.archlinux.de/packages#query=vim
It shows 71% (for vim-runtime), that is a lot higher than ~20% for
emacs.
Amusingly, https://pkgstats.archlinux.de/packages#query=nano tells
us that nano clicks at 80%, which makes it the editor with the
largest number with your yardstick ;-) [*2*].
In any case, I think it is a worthy goal to ship a sample set of
"vimrc" entries that people can readily accept for their use. It
also is a reasonable "feature request" to consider doing something
similar to "editorconfig" to give other editors similar convenience.
[Footnote]
*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.
Note that I do not doubt vim is popular. It is popular and it makes
sense to include it in the set of "first class" editors that deserve
priority treatment when we allocate engineering effort to support.
I just do not think these graphs are the best supporting material
for the claim you made "the most widely used editor by developers".
next prev parent reply other threads:[~2020-12-09 6:55 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 [this message]
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
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=xmqqlfe731vh.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=emilyshaffer@google.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--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).