On Mon, Sep 16, 2024 at 5:41 AM 'rengel' via leo-editor < leo-editor@googlegroups.com> wrote:
BTW: Is there a safe way to include "<<...>>" structs in source code in the > body pane? How can Leo be prevented from looking for such structs in the > body pane? > <<...>> *always *means a section reference for @file nodes. There are no exceptions. This constraint is the *only* way of reading @file nodes reliably, so this constraint is a fundamental part of Leo. <<...>> may be just text in other kinds of @<file> trees. See Leo's reference for details. In the meantime I was able to repair the Leo file using an external editor. >> It contained some Erlang source files. The Erlang source code uses some >> data structures that look like Leo section references '<<...>>'. That >> caused some hiccups so that in the end Leo wasn't able to parse the Leo >> file correctly and put everything under one node. Basically, the repair was >> just removing the t nodes that contained Erlang code. >> > Glad to hear it. It's possible that the Erlang importer may be the culprit. 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS1AHAVQKNrpL%2BgqH8EhnASgjo2B3LMW%2BrW_EQ0Gw_2Thg%40mail.gmail.com.
