On Sun, Jun 28, 2020 at 8:11 AM Edward K. Ream wrote: > leoInteg's colorizing code will likely use an LSP. The LSP can be written in python, which means a repackaging of Leo's existing colorizing code may be possible.
Yes, Leo's LSP *could* be written in python, but that may not be the easiest way. Leo's LSP will likely delegate most coloring to vs-code's default colorizers for the @language in effect. This would likely be easiest to do in ts. Leo's LSP would (sometimes!) break body text into chunks consisting of a range of lines to be colored by the same language, with only *Leonine lines* (lines containing Leo directives and section references) being colored using syntaxes/leoBody.tmLanguage.json. *It should be possible to avoid re-calculating chunks on every keystroke*. After all, existing vs-code colorizers almost certainly do not re-tokenize the entire file on every keystroke. Figuring how to avoid this recalculation is next on my study list. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS0xk526f3b-t7FnSXn1WVQU5ecC%2BvDRe_xW6TaB2yiaFQ%40mail.gmail.com.
