On Jan 24, 10:38 am, Edward K. Ream edream...@gmail.com wrote:
I'll be continuing to hack on Leo's settings-related code today...
I spent much of yesterday making clear, in the source code, the types
of elements contained in the list returned by config.getShortcut and
other methods. Indeed, I
On Jan 25, 6:12 am, Edward K. Ream edream...@gmail.com wrote:
Yesterday in the bath I saw an elegant way to update merge two bindings dicts.
[snip]
For any dictionary d, d == uninvert(invert(d))
The invert and uninvert operations can *not* be applied to arbitrary
dicts. Invert applies only
Close all nodes, save .leo file, commit only the portions that need to be
shared (i.e., don't commit any personal clones of nodes you may have made for
your own projects).
I do not understand. What is the meaning of the word close in this
context? Do you mean to collapse the outline?
How
On Wed, Jan 25, 2012 at 6:12 AM, Edward K. Ream edream...@gmail.com wrote:
We compute the result, merged_d, as follows::
Actually, d.update() updates d in place: it does not return a value.
Thus, the code must be::
inverted_old_d = self.invert(old_d)
inverted_new_d = self.invert(new_d)
On Wednesday, January 25, 2012 9:47:52 PM UTC+7, Josef wrote:
I do not understand. What is the meaning of the word close in this
context? Do you mean to collapse the outline?
How to you commit portions? I was talking about the Leo file, so I can
only commit the whole Leo file, or
