On Tue, Jul 8, 2008 at 7:33 AM, Edward K. Ream <[EMAIL PROTECTED]> wrote: > > > On Tue, Jul 8, 2008 at 7:29 AM, Edward K. Ream <[EMAIL PROTECTED]> wrote: >> >> 1. First, I'll create @auto for all the files of the pypy project in >> which I have an interest. An already-existing script will help me do this. > > There are often minor problems that must be corrected before @auto will > import a python file "perfectly", typically tabnanny problems or > underindented comments. It would be necessary to convince the pypy > community to allow me to fix these minor problems so that I can use Leo.
Or convince Leo to offer the option to not chunk files upon importing. My thoughts on chunking - it is a matter of taste, each coder has their own conception of how a source file should be chunked, if at all - I find that I read more code than I write, and the chunking interferes with grasping what is going on. I like to scan the file top to bottom, not click in and out of nodes. Clearly, others have different cognitive styles. I think the nodification Leo offers is best suited to writing, but again, you won't get a consensus. > Presumably, that would be easy to do: there should be no reason why a > project should be committed to either inconsistent whitespace or > underindented comments. > > EKR > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
