As far as getting syntax coloring of body text in vscode, just have leo give you what language it considers the body to be and have your extension change it to that language. That should be possible as you can click on the "applied" language in thy status bar at the bottom of vscode and change to another language from the list that pops up.
Tom On Friday, June 12, 2020 at 9:55:48 PM UTC-4, Félix wrote: > > The second option > > > Follow the example of the pygments code, and alter the js coloring code > to handle Leo directives and section references. > > Is what I'm going for to get some coloring started in leoInteg. It's > something that may get revisited later as the feature grows in maturity... > > I'm going to define the same languages dependant highlighting as leo, > along with the syntax highlighting for @xxx directives and <<xxx>> > references by converting to the formats required by vscode :) > > I'll start with the directives and references to get the generic 'Leo' > feel of an opened body pane. > > thanks again for the tips :) > > > On Friday, June 5, 2020 at 6:08:42 PM UTC-4, Edward K. Ream wrote: >> >> >> >> On Thu, Jun 4, 2020 at 4:02 PM Félix <[email protected]> wrote: >> >>> Thanks! >>> >> >> You're welcome. >> >> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/fbd5c4b8-b780-40ca-8509-bdda7a6ee9b1o%40googlegroups.com.
