I haven't tried it but Leo has an alternate JSON file format. That ought to work for the erlang files.
On Monday, September 16, 2024 at 6:41:37 AM UTC-4 rengel 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? > > On Monday, September 16, 2024 at 12:38:32 PM UTC+2 rengel wrote: > >> Thanks for your suggestion! >> >> But this is the only node. In its body text it contains hundreds of othe >> nodes wrapped in an xml file. So deleting that node would delete all the >> contents of this Leo file. >> >> 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. >> >> I was just about to report this solution, when I saw your answer. Thanks >> again! >> >> On Monday, September 16, 2024 at 9:33:08 AM UTC+2 Edward K. Ream wrote: >> >>> On Mon, Sep 16, 2024 at 12:56 AM 'rengel' via leo-editor < >>> leo-e...@googlegroups.com> wrote: >>> >>>> I have a leo file stored in 'D:/dev/.leo/Dev.leo'. >>>> >>>> When I open this file with Leo (on Windows 10), I get >>>> >>>> '@edit D:/dev/.leo/Dev.leo' >>>> >>> >>> Strange things happen. I would just delete the 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/2d02e537-7df6-4aed-8147-1ccfab4b2889n%40googlegroups.com.
