Edward K. Ream
Edward K. Ream
@boltex Doh. I see that "generic" output region shows the Leo log, so there is good reason for LeoJS's existing behavior. To answer your question: I was referring to the...
@boltex Alternatively, perhaps the Leo console could be moved to left-hand area, the area that contains 'Outline', 'Timeline', etc. Again, this can wait until well after LeoJS 1.0.
@boltex Thanks for this change.
@boltex Thanks for your comments. Imo, part 2 of this issue should be fixed for LeoJS 1.0. **Part 1**: Desktop Leo can color individual lines with different language *within the...
@boltex There two workarounds for the pattern: ```python @language rest notes about an issue @language python ``` **Workaround 1**: Put the notes in a separate node, with a single `@language...
@boltex I thought perhaps you had made such an invalid assumption. Restoring Leo's exact coloring code is likely the only way to fix this issue.
@boltex The intended behavior is that an **ambiguous** node (a node with multiple `@language` directives) does not affect the syntax coloring of its *descendant* nodes. So whether descendant nodes are...
@boltex I'm glad the fix was straightforward.
@boltex I found the same links. Perhaps you could say hello to their projects :-)
@boltex LeoJS doesn't need docutils in Typescript. LeoJS probably *does* need something like [sphinx-js](https://github.com/mozilla/sphinx-js). **docutils** Unless I am seriously mistaken, LeoJS does not need docutils. Indeed, `LeoDocs.leo` contains these settings:...