On Mon, Apr 27, 2015 at 9:23 PM, 'Terry Brown' via leo-editor <[email protected]> wrote:
> > > I've found one letter abbreviations to > > be a nuisance. For example Edwards recent example of e;; is not > > compatible with date;; > > > This is a bug which I'll fix asap. The abbreviation matcher should > > prefer the longest match. It's probably one or two lines of code. > It was, but I got involved in some cool additions. Almost ready to push a fix. once you define > > @data > > abbreviations and / or @data abbreviations-subst-env in > > myLeoSettings.leo, you're isolated, for better or worse, from updates > > to these nodes in LeoSettings.leo. You hint at a partial solution when you mention composing @data nodes from their children. Both @data abbreviations and @data abbreviations-subst-env should be defined that way. The next push will do that. So you could put all your overrides in a personal node, and merge (by hand) that node into your @data nodes when the global nodes change. Not perfect, but not bad. Indeed, there is no urgency to staying current if you are satisfied with what you have. I am not wild about complicating settings even further. Settings are already too complex for me to understand fully. Any more features would make life harder for newbie and guru alike. Imo, a better way would be to improve diffs of Leo outlines. The --diff option is a fairly feeble start. Improved diffing of outlines would highlight the new stuff so you could merge it. Improving diff is on the list for 5.2. 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.
