It's always good to pay attention to seemingly small details.  Some of them 
matter a great deal. Some hardly matter at all. Having said that, Leo is 
now at the stage, imo, where such issues are not terribly important overall.

There are much larger questions that we can be asking about how outlines, 
data, programs and scripts interact.  These questions might suggest new 
coding patterns, plugins and commands. This is what I would like Leo's core 
developers to do most of the time.

So yes, details *are *important.  Misspellings, documentation errors, UI 
glitches, cleaning the code, whatever.  But let's not focus exclusively on 
the minutia.  Leo will succeed or fail based on the larger issues.  

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 [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.

Reply via email to