Closed d5ous closed 5 years ago
Yes, it's deliberate. The library just assigns classes corresponding to the tokens, and leaves all styling to the styles.
That's a decision that could be revisited, but we'd have to make the Token type more complex and I am not sure it's worth it.
To record a sense of what a refactor would buy: there seem to be about 400 syntax items affected across a broad range of file types in the syntax highlighting set that ships. The whole (presumably importable) set in KDE syntax-highlighting has more like 900 instances. How many of those really matter undoubtedly depends on who you ask, but "not much in most cases to the majority of people" seems like a fair expectation.
The number of items that create direct cognitive dissonance (like strong that isn't bolded) is much lower, found in the expected cases, and spread over perhaps half a dozen files that could be addressed individually.
With input file
headings.md
having contents:And command line:
I expected the headings to be colored with a style corresponding to
dsFunction
and bold, based on what's contained inmarkdown.xml
:Instead, only the function style seems to be applied, for example:
The above was produced by an install of skylighting performed via stack today (v 0.7.7), and is consistent with what I'm observing in pandoc. It appears to be systematic for
bold=
,italic=
, etc.Assuming that the above behavior is deliberate (and that I haven't simply misunderstood/misconfigured something), it might be worth a mention in the readme.