Closed ghost closed 7 months ago
I'm not interested in this feature, if a file extension is incorrectly not supported users should report it and get a global fix for everyone. "Local" fixes aren't the correct solution. If anyone wants to support a new language already have all the tools provided by ecode to do it, even exporting a base language from the command parameters provided by ecode:
--export-lang-path=[export-lang-path]
Export language definitions to the file
path. If no "export-lang" is defined it
will export all languages available.
--export-lang=[export-lang] Comma separated language names to export
its language definitions.
"export-lang-path" must be defined.
Extension
config.cfg
to add something like:Note: I choose
vala=csharp
as an example because these two languages are very similar and I assumed that built-in syntax highlighting for Vala is not yet available.