Hi Edward, I am the one who originally requested this feature, because I thought it would better represent the structure of a large document. I used it for a while, but since there are problems with it I accept if you disallow this feature (child @clean nodes cannot have themselves other node children, and there seems to be a problem when editing the files outside Leo as well). I think it is better not to have a feature unless it works reliably. I fear there are not that many people, who like me work on large tex documents together with several other people, so I am all right if you scrap this feature.
A good workaround for me is to use links (with backlinks): I insert a link to the @file node at the node where the corresponding \input sits. - Josef On Sunday, May 5, 2019 at 3:25:54 PM UTC+2, Edward K. Ream wrote: > > Don't panic: I'll allow at least a week for comments here. Imo, #1134 > <https://github.com/leo-editor/leo-editor/issues/1134> is minor, no > matter how it turns out. > > Is anyone using nested @<file> nodes successfully? > > Does anyone really need nested @<file> nodes? > > 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 post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
