Florian Neumann

> I believe all EidorConfig features are optional. It depends on the tool you're using to enforce the EC rules. A linter wouldn't allow you to drain misaligned files into...

@mstruebing - we already worked on a ini parser in preparation for a Rust/WASM core of EditorConfig. It is more or less experimental yet. It may be useful for you:...

@cxw42 thank you for asking 🙏 - i'm a bit confused. Let me try to recap it in my words: ### Issue 1. You'd like to use defaults over file...

If you're working in a project having a "root" EditorConfig the creator of this config claims that this EditorConfig-File should be authoritative. If this EditorConfig misses any configuration of a...

I feel like you'd like to "optimize" how to specify EditorConfig settings. I take one example, the `project/extern/.editorconfig` and the tab versus space definition. Given the assumption this is a...

> I really, really, really: > > * don't want to have to click through dumb menus or JSON files to edit VS Code tab width or other basic setting...

I did a (very) small research on how editors are handling this. I fear that currently the available settings differ a lot between the different implementations between the spell checkers....

Thank you very much for your statements @anguslees! I will try to enlighten the "perversion" for you: the EditorConfig exists longer than the specification, which is an attempt to make...

Thanks for the cc – in my opinion this is a glitch in the implementation of INI-parsers, caused by a missing INI specification (something one-ini) aims to solve. I think...

@jedmao I recall we had some discussions about the handling of comments. Did we already settle a decision or were the Rust tests a first step to adopt EditorConfig specs?...