Closed mrmeszaros closed 1 year ago
This conflict is caused by the design of EditorConfig's syntax.
EditorConfig.sublime-syntax includes scope:source.ini
and provides a hidden simplistic INI.sublime-syntax for that scope.
A File Icon doesn't (can't) accept hidden syntaxes as replacement for its dummy syntaxes.
Thus it can't be fixed by A File Icon without causing other issues.
Easiest solution would be to also install the "INI" package, which also provides more sophisticated highlighting for ini files.
Otherwise changes to EditorConfig package would be required, but I wouldn't be surprised its current design to be meant for making use of INI package, optionally.
@deathaxe I installed the INI
package, however, it also defines an EditorConfig
syntax, which results in two Set Syntax: EditorConfig
commands.
This is quite confusing - as the two syntaxes produce different colors. This is in turn caused by different scope names.
I have compared the two, and the one from the INI
package seems more developed - also stated in https://github.com/jwortmann/ini-syntax/issues/16#issuecomment-1606256652.
I propose two options to solve the issue:
EditorConfig
syntax definition with the one in the INI
package.
After that, the INI
package could drop the EditorConfig
syntax definition.
INI
syntax as well (to match)INI
package as a dependency - this is done with other packages as wellINI
, like indent_style
integration with SublimeTextI would prefer keeping this package separate and depending on INI
for the syntax definition
Either way, it would solve the duplicate command issue.
Also, I might create a separate issue for it, should this move forward.
You are right, ideally both packages would provide independent syntaxes to avoid conflicts or duplication. EditorConfig syntax just being an INI file is probably the root cause.
That's unrelated with A File Icon however and would be resolved by those package's authors/maintainers.
I am terribly sorry - for some reason I was under the impression I am commenting under the EditorConfig
.
So please disregard my previous comment - it IS unrelated, and should be resolved by the EditorConfig
and INI
folks.
Thanks again for the help and patience and understanding!
After installing this package the
.editorconfig
file does not show a proper syntax highlighting.Expected Behavior
Using custom file icons should not affect the syntax highlighting.
Current Behavior
Although the correct syntax is selected - the
.editorconfig
file has no syntax highlighting.Steps to Reproduce (for bugs)
A File Icon
(this) packageEditorConfig
packageCreate an
.editorconfig
file - for example:Context
Currenty I have to chose between the nice icons and proper syntax highlighting for the
.editorconfig
file.Your Environment
The
Package Settings → A File Icon → Environment
command does not exist anymore.Here is the console output with
"dev_mode": true
: