While you are at it, how about moving the @language python directive to the start of the node's body? Putting it at the end just confuses everything for no advantage, and it's confusing for a human reader too. For colorizing line by line the language declaration pretty much has to happen at the start of a block with that language.
On Sunday, November 10, 2024 at 9:01:16 AM UTC-5 Edward K. Ream wrote: > On Saturday, November 9, 2024 at 3:08:15 PM UTC-6 Edward K. Ream wrote: > > In other words, I am *already* eating my own dog food (in the PRs branch). > > It's easy to ignore the remaining coloring glitch. > > > I spoke too soon. Coloring markdown improperly quickly becomes super > annoying. My workaround: > > - Temporarily comment out the trailing @language python in my project > organizer node. > Doing so restores correct colorizing. > - Add @language python to all nodes that are (or could become) children of > the project organizer node. > > 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 visit https://groups.google.com/d/msgid/leo-editor/3084be2c-6361-4c2c-a584-e5830a34ee47n%40googlegroups.com.
