search

SpartanJ / ecode

Lightweight multi-platform code editor designed for modern hardware with a focus on responsiveness and performance.
MIT License
941 stars 13 forks source link

Set lexer for custom file extension in `config.cfg` doesn't work #246

Closed ghost closed 7 months ago

ghost commented 7 months ago

I followed the instruction here: https://github.com/SpartanJ/ecode/discussions/194

I edited config.cfg to add winlib=shellscript. Doesn't work. This means I can't register new file extensions in config.cfg.

SpartanJ commented 7 months ago

That configuration is not for setting a custom file extension, but for setting the default language for a file extension (when a file extension can represent more than a single language). Currently it's not possible to register custom file extensions.