Yeah, git clone ... is such a simple way to look over a shoulder if not get involved.
The code reflects a couple of my proclivities: - interest in timestamping: I tend to work on a widely scattered set of files/projects, do nothing for a few weeks. Timestamping will some day help me rejoin the prior dev stream. - interest in treating Leo files as datastores, hence emphasis on LeoBridge, accessing via API - wrapping Leo code in code which fits my mental model better, someone better versed in Leo than myself would probably prefer going directly to Leo code instead of the wrappers. On Sat, Dec 6, 2014 at 9:54 AM, Edward K. Ream <[email protected]> wrote: > On Sat, Dec 6, 2014 at 8:57 AM, Kent Tenney <[email protected]> wrote: > >> So, I did a bit of cleanup on a collection of Leo-related >> code and pushed it to github. > > > Thanks for this. I'll look at it in more detail soon. > > BTW, it seems to me that git clone is miles ahead of any other distribution > method. > > 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. -- 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.
