Ulrich Mueller <u...@gentoo.org> writes:

> [[PGP Signed Part:Undecided]]
>>>>>> On Fri, 24 Mar 2023, Florian Schmaus wrote:
>
>>> Then it looks wrong, conceptually. Or would it be o.k. if I committed
>>> ebuild-mode.el to the top-level directory of the Gentoo repository?
>
>> I do not think the comparison with ebuild-mode.el is sound:
>> ebuild-mode.el appears imperative, while .editorconfig is declarative.
>> Furthermore, and more importantly, ebulid-mode.el is (more or less)
>> editor-specific, while .editorconfig is editor agnostic.
>
> Sorry, a better example for Emacs would have been .dir-locals.el in
> the top-level directory.

Projects can and do include mode lines and .dir-locals.el.

>
>> That said, given how coupled ebuild-mode is with gentoo.git, I
>> personally would not mind if it where managed in the same repository.
>> [...]
>
> That's not going to happen, because it simply doesn't belong there
> (and neither does any other editor configuration IMHO).

This comes across as arguing for the sake of it if you disagree on
principle. Do you have constructive feedback about the actual contents
of it? Would you like to know more about the available options?

>
>> In any case, I am a fan of .editorconfig. Hence +1 from me for adding
>> it to gentoo.git.
>
> But what does it do, effectively? Apart from the common-sense settings
> (utf-8, no trailing whitespace, etc.) which should be the default for
> every editor, the only setting specific to ebuilds is to enable tabs.
> Then again, it doesn't even say that they represent 4 spaces.

That's just because I forgot to put that bit in. Also, these aren't
default for every editor, even if you wish that were the case.

>
> Ulrich
>
> [[End of PGP Signed Part]]

Attachment: signature.asc
Description: PGP signature

Reply via email to