git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Add project-wide .vimrc configuration

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 9, 2020, 06:54 UTC
Message-ID
<xmqqlfe731vh.fsf@gitster.c.googlers.com>
In-Reply-To
<CAMP44s0W3En0ZuNfBOOZhfeFUeFRvEFs7khAFRraocuDaFpbNA@mail.gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
Show 11 quoted lines
>> 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".

Previous: Felipe ContrerasNext: Felipe Contreras
Message 11 of 15 in “Add project-wide .vimrc configuration”
  1. Add project-wide .vimrc configurationFelipe Contreras, Dec 9, 2020
  2. Junio C HamanoDec 9, 2020
  3. Felipe ContrerasDec 9, 2020
  4. Aaron SchrabDec 9, 2020
  5. Junio C HamanoDec 9, 2020
  6. Felipe ContrerasDec 9, 2020
  7. Denton LiuDec 9, 2020
  8. Felipe ContrerasDec 9, 2020
  9. brian m. carlsonDec 9, 2020
  10. Felipe ContrerasDec 9, 2020
  11. Junio C HamanoDec 9, 2020
  12. Felipe ContrerasDec 9, 2020
  13. Junio C HamanoDec 9, 2020
  14. Felipe ContrerasDec 9, 2020
  15. Randall S. BeckerDec 9, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.