On Mar 27, 1:28 pm, "Edward K. Ream" <[email protected]> wrote: > On Fri, Mar 26, 2010 at 1:03 PM, zpcspm <[email protected]> wrote: > > I've come to a point where I'm realizing it would be nice to have a > > meta-outline that holds references to another outlines. > > I don't work that way, although it's certainly feasible. The > following isn't meant to discourage you, but to suggest an > alternative. > > Instead, I typically one-or-two-word batch files/scripts to open .leo > files in separate consoles.
I see. When writing code, I have leo opened + a terminal where I manually run misc tools (like pylint, clone digger, coverage.py + versioning-related commands like commit). Having leo store its outline- specific data as comments in source code proves to be a wise idea - I can directly run external code-massaging tools against @thin files without having to perform an intermediate step everytime (in a scenario which would involve a database backend for outlines, this would be harder). -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
