This is related more on @file than on @auto. Please bear with me if i'm being too persistent but looking at the outline metadata embedded in an @file node's external file, it got me thinking if it's possible to store those sentinels in the parent node with additional information on which line in external file they apply. Then the @file read logic will reference this data in the parent node when reading in the external file, creating a node when encountering a line which has a corresponding stored sentinel. These sentinel data stored in parent node can then be exported into a file. When imported into an @file node, it will create the original outline based on the same external file.
The reason for my persistence is that I love the code outlining and organizational possibilities that can be done with @file node but I don't like the sentinels that are embedded in the source file. It kinda makes the code look cluttered when I'm editing the code in an external editor like sublime which is my main editor of choice nowadays. That's why when I went back to using leo a few months ago, I have used mostly @auto since I don't edit code in leo. btw, I have no idea what @auto-view does and I haven't had the time to look into it. Eric -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
