Thank you for the quick overview of your methods. On Saturday, December 3, 2016 at 5:50:20 PM UTC-5, Edward K. Ream wrote: > > On Sat, Dec 3, 2016 at 3:58 PM, john lunzer <[email protected] > <javascript:>> wrote: > >> >> Like djc, I found Leo's source a little overwhelming but as I understand >> you've said that even you don't now remember all of Leo's source, which >> means you must have valuable methods for finding and fixing bugs in Leo >> that don't entirely rely on source knowledge. I'm greatly interested in >> those techniques. >> > > What I do have is a feel for where things are in Leo. I know, for > example, that leoApp.py contains: > > - Startup code, > - Language tables, > - Leo's globals (g.app ivars) > > I know that Leo's oldest commands reside in leoCommands.py, as does the > all-important Commander (c) class. Newer commands reside in > leo/commands/*.py. > > I know, generally, what *every* > > file in Leo does, and I have some feel for what the shape of the code > is. This should come with experience. > > However, when doing something complicated, for instance something like > #340 <https://github.com/leo-editor/leo-editor/issues/340>, > reload-abbreviations, I do a massive amount of searching using cff. There > is no substitute for really understanding code, at least for a short time > ;-) Later, it all devolves to mush, but a feel for the general shape of > the code remains. > > HTH. > > 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
