I used to stick with the Default Monokai color scheme, but not until discovering your Agila Monokai Extended scheme. It is really an awesome scheme, but recently I found some issues with it.
TLDR
Default Monokai
Agila Monokai Extended
Long Explanation
As you can see from the screenshots above, Agila Monokai Extended (AME) failed to highlight several parts of the code or the console message, while the Default Monokai was able to handle. As described in Sublime Text's official document on Scope Naming:
MINIMAL SCOPE COVERAGE
The following is a recommended minimal set of scopes to highlight. Adding extra may result in a slightly improved experience, however being too specific will result in a color scheme that often only looks good for one or two syntaxes.
...
variable.function
Therefore, it is important to have highlightings for the variable.function scope. Aside from that, I was wondering could there be more cases that the Default Monokai could handle but not AME? So I compared AME's color scheme side-by-side with the Default Monokai's, and found that the following scopes were also ignored by AME:
The first two scopes, punctuation.definition.annotation and variable.function, variable.annotation, correspond to the first and third screenshot (Python). These affect the annotation (@) and the function invocation.
The entity.name.filename and message.error scopes correspond to the second and fourth screenshot. These are the make output in the build panel, which could be replicated by first open a folder with Makefile, and then run build.
Description
I used to stick with the Default Monokai color scheme, but not until discovering your Agila Monokai Extended scheme. It is really an awesome scheme, but recently I found some issues with it.
TLDR
Default Monokai
Agila Monokai Extended
Long Explanation
As you can see from the screenshots above, Agila Monokai Extended (AME) failed to highlight several parts of the code or the console message, while the Default Monokai was able to handle. As described in Sublime Text's official document on Scope Naming:
Therefore, it is important to have highlightings for the
variable.function
scope. Aside from that, I was wondering could there be more cases that the Default Monokai could handle but not AME? So I compared AME's color scheme side-by-side with the Default Monokai's, and found that the following scopes were also ignored by AME:punctuation.definition.annotation
andvariable.function, variable.annotation
, correspond to the first and third screenshot (Python). These affect the annotation (@
) and the function invocation.entity.name.filename
andmessage.error
scopes correspond to the second and fourth screenshot. These are themake
output in the build panel, which could be replicated by firstopen a folder
with Makefile, and then runbuild
.