On Monday, October 10, 2022 at 5:00:41 PM UTC-5 [email protected] wrote: > It's possible to imagine doing more with the text of Leo nodes, such as > supporting syntax checking during typing for a range of languages.
Thanks for the link. I just briefly scanned the post about Lezer. It illustrates the joy of engineering :-) Leo's syntax coloring and importers are highly optimized examples of the general parsing/tokenizing problem. Both have gone through multiple iterations. Leo's syntax coloring is (indirectly) driven by jEdit language description files. Leo's code depends on the details of Qt's syntax coloring classes, so adapting Leo's code to vs-code might be challenging. Leo's importers use per-language syntax (token) tables. leoJS could probably use the importer scheme without major changes. I'll leave my comments at that for now. 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/e1667bd7-7d72-463e-8a34-a01c99c53f57n%40googlegroups.com.
