I'm working to simulate EditorConfig support with ec2hx. It works by generating a workspace helix configuration that matches the editorconfig.

The hard part is arbitrary glob sections in editorconfig, because Helix only supports configuration based on languages, not globs. For example, the linux editorconfig has two different indentation styles for python based on which subdirectory the python files are located in...

My solution is to generate synthetic language definitions with the glob as its file-types. The rest of the configuration is copied from the actual language.

In order for syntax highlighting to work, I need to generate textobject queries for the synthetic language. The content is simply ; inherits: <language>, no issues there. But helix doesn't read from a workspace runtime directory, i.e. proj-dir/.helix/runtime. That means I have to generate the textobject queries into the user configuration runtime directory, e.g. ~/.config/helix/runtime. I would like to avoid that, I myself hate tools that vomit autogenerated garbage into my config directory.

Unless there are objections, I will try to implement reading from a workspace runtime directory.