@pmatilai The project was started in late 2011, like many such things it was a
bit slow to gain traction — between needing plugins or integrated support to be
developed for various editors, and needing to convince users it was worth
bothering with.<sup>1</sup> But it's really started to pick up steam in the
past few years. These days, GitHub code search reports [893,000 files matching
the pattern
`/\.editorconfig$/`](https://github.com/search?q=path%3A%2F%5C.editorconfig%24%2F&type=code)
in its indexed public repositories. Now including rpm!
### Notes:
1. Which included having to overcome the pushback of "Why do we need this? My
files have modeline comments in them." (Which is _somewhat_ valid, but
modelines (a) don't help with newly-created files, unless the author makes sure
to add the appropriate modeline, (b) are an impossibly cryptic solution
compared to the EditorConfig INI format, and (c) aren't nearly as widely
supported as `.editorconfig` is now.)
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/3219#issuecomment-2265676860
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/3219/c2265676...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
