Does ecode support EditorConfig?

[ghost]

Can I bring my .editorconfig from VSCode?

[ghost]

I’m more interested in having ecode generate this .editorconfig file for me. I had never heard about it before, but I used to see it present in many repositories on GitHub. I didn’t bother to learn more about it until now. Since I don’t use other editors, I don’t have any existing .editorconfig file to bring with me. However, I don’t dismiss the idea of running other editors in the future. So it would be great if ecode could generate this file for me. I don’t think I’m committed enough to learning the syntax to write my own .editorconfig manually.

[SpartanJ]

Can I bring my .editorconfig from VSCode?

ecode currently does not support EditorConfig spec. I wouldn't be hard to support but it's not very compatible with the current existing configuration options within the editor, in the sense that configurations would need to be separated one from the other and the editor would need to prioritise one. In that case I could honor the .editorconfig configuration and that's it, internal ecode configurations would be ignored if any rule from the .editorconfig applies to the opened file. I think most editors do basically that but I haven't investigated, I've never used EditorConfig although I'm aware of it and know the spec.

I’m more interested in having ecode generate this .editorconfig file for me.

That's not reasonably feasible given the EditorConfig spec. Essentially EditorConfig works with pattern matching and it's totally configurable so it's not very compatible to do the inverse work since there's no a strict rule to which patterns one should use for any file (and saving a single rule per file is contrary to the intention of the spec and very bad for manual editing), also .editorconfig files can be sparse over the project directories which also overwrite the parent folder rules (it's designed to mimic .gitignore files). So that for sure is not going to happen.

BTW this is the spec

[ghost]

I did a little search with AI. Yes, the idea of .editorconfig takes priority and overwrites the local settings of the editor is absurd to me. But it seems VSCode can generate .editorconfig (via an extension also by EditorConfig). It seems .editorconfig needs this ext to be enforced.