On Thursday, July 16, 2020 at 7:51:47 PM UTC-5, Félix wrote: > Just small remarks for using "real" JSON with Leo:
When I awoke this morning I understood several aspects of Leo and json that I never appreciated before. Most of what I am about to say is implicit in Félix's remarks, but I didn't fully understand them until now: 1. json does not support comments, so Leo really can not properly embed Leo sentinels in .json files. In other words, you can' *reliably *use @file on .json files. 2. You *can* use @clean on .json files without any problem! The @clean update algorithm (The Mulder/Ream algorithm) uses "pseudo sentinels" internally. The specific comment delimiter used *doesn't matter,* because only the algorithm uses the sentinel. The comment delim never appears "outside" the algorithm. 3. The @button mark-changed script won't work well with .json files. It can't detect nodes that are candidates for being split. The script uses parse-body to mark nodes that are candidates for being split. Alas, parse-body uses the importer for the language that is in effect, but there is no .json importer, and never can be such a thing. Boo hoo. 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/fe8fefbe-59fd-47e8-b7e2-0163f4c244beo%40googlegroups.com.
