This is why @auto will always be important. @clean doesn't replace @auto, it's a different set of features with cost and benefit.
On Tue, Feb 24, 2015 at 5:48 AM, <[email protected]> wrote: > Thanks for the clarification! > > > >>> Did you try this on Leo itself, having some hundreds of thousands of >>> lines in one Leo file? >> >> >> No, because we aren't going to use @clean for Leo. >> >> >> I tried it on a significant project: pylint. Loading a single .leo is >> fast, regardless of size. I compared loading the entire project with @file >> vs. @edit, without significant difference. >> > > > Does this mean that some projects are not suitable for @clean? > > What would be the best way to proceed to bring a really large project with > thousands of files (i.e. Eric or PyQt or only the PyQt documentation) under > Leo control using @clean? > How would the import of such a project work? > Would Leo decide which files to save with @clean and which files to keep > outside of Leo? > > If you want Leo to appeal to wider audience of programmers Leo should be > able to import 'legacy' projects without hassle. > Nobody likes to work with two development environments: an old one for > legacy projects, and Leo for new projects. > > Reinhard > > > > -- > 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/d/optout. -- 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/d/optout.
