On Friday, December 10, 2021 at 8:36:22 AM UTC-6 [email protected] wrote:
> This link may be of interest. It is about reconstructing a python file > from its parse tree. Maybe a few changes to the code generator would do > the job: Thanks for the link. Last night I realized your comments about parsing (using leoAst.py) were more apt than I first thought. However, using any parser, including leoAst.py, seems like overkill. Remember that my legacy python importer (now resurrected in the ekr-importer2 branch) doesn't really have a parser problem. My importer handles all normally indented code correctly. Just for fun I'm going to try once again to have the importer handle strangely-indented code. Vitalije's code generation shows that there is no need to generate outlines more than two-levels deep. That insight may help me simplify the code generators. Vitalije's problems may be a bit different, but I'll let him speak for himself. 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/acaea226-e6f9-49b8-ab4e-b6193f301daan%40googlegroups.com.
