[mqus]

Most repositories I work on don't have only one language. They have at the very least two, like the main language and maybe markdown for README files, then configuration like .ini or .toml, json stuff, yml, xml, etcpp. And then you might have bash scripts, Dockerfiles, other build tool languages, etcpp. And those are only text files. You probably will also have images, maybe zipped stuff, office documents and more, all not the "core" repository content, but stored nearby and versioned alongside.

Building a hyper-focussed tool won't be very useful, expect to at least rudimentarily support other file types.

[willow8349]

This doesn’t really detract from my point - the “best” tool tool would use knowledge of python for python files, json for json files, and so forth. I think you’re just saying you’d want multiple of these rolled in a single tool as opposed to standalone, which is fair. I think any tool would have to be compatible with git /layer on top of it so it’s available as a fallback

[fanf2]

Off topic, but “etcpp” is a new one for me. Wiktionary suggests it is German, which amuses me because I write “etc. usw.” to mean the same thing.

[mqus]

whoops :D thought it was more international than this, since its pretty much as latin as etc. Interesting!

[jorams]

I read it as a little joke referring to C++, for what it's worth.

[maleldil]

What's the difference between etcpp and etc?

[fanf2]

The pp implies there are manny more things, as opposed to just some more things. https://en.m.wiktionary.org/wiki/etc._pp.

[mqus]

sibling is right, although for me its mostly a habit, I rarely use etc.