Closed KyleOndy closed 6 years ago
KyleOndy
commented
7 years ago Thinking out loud here...
Would it be preferable, or possible even, to make KDE's repo a submodule or sub tree of this repo so lessen the maintenance burden on adding and updating the xml files?
This would let KDE do the heavy work of managing the xml files, while this repo exposes them all to the haskell world.
jgm
commented
7 years ago I don't want to bring them all in; it already takes a long time to compile skylighting, and the library gets bigger each time we add a syntax. So I try to restrict to a subset of the most used ones. You can always add others dynamically if you need them.
+++ Kyle Ondy [Sep 28 17 16:24 ]:
Thinking out loud here...
Would it be preferable, or possible even, to make KDE's repo a submodule or sub tree of this repo so lessen the maintenance burden on adding and updating the xml files?
This would let KDE do the heavy work of managing the xml files, while this repo exposes them all to the haskell world.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, [1]view it on GitHub, or [2]mute the thread.
References
KyleOndy
commented
6 years ago That sounds like a reasonable response to me. Is there any existing documentation or examples on loading additional syntax files dynamically?
If there is not, I will try and create some.
jgm
commented
6 years ago If you're using pandoc, the upcoming 2.0 release will have a --syntax-definition option.
If you're using this as a library, then see the Haddock documentation.
What are the plans for styles that exist the the KDE repo but not his repo?
Is it as simple as what was just done for the powershell syntax in #16?
If so, I would be happy to put in the work to incorporate them, either with a single PR or one each.
The list of filetypes in KDE but not skyligthing follow: