On Monday, March 9, 2015 at 7:35:19 AM UTC-5, Edward K. Ream wrote:
This is an Engineering Notebook post (notes to myself) concerning
https://github.com/leo-editor/leo-editor/issues/149
Clones can revert changes made by git discard even with --no-cache
You can safely ignore this post
Early this morning I completed the first phase of the fix for bug 149:
Clones can revert changes made by git discard even with --no-cache
https://github.com/leo-editor/leo-editor/issues/149
The question is, how to push the fixes?
= Background
The fixes are a grand revision of leoAtFile.py,
On Tue, 10 Mar 2015 06:05:55 -0700 (PDT)
Edward K. Ream edream...@gmail.com wrote:
Early this morning I completed the first phase of the fix for bug 149:
Clones can revert changes made by git discard even with --no-cache
https://github.com/leo-editor/leo-editor/issues/149
The question is,
The code that issues recovered nodes warnings must know whether v.b has
been inited previously or not. Alas, the present code (in
at.terminateBody) uses this code instead::
if v != at.root.v and old != new:
# Not exactly correct. Old could be empty.
# However, it appears to
The new code is pretty much as described here:
ENB: A dict creates virtual temp status bits
https://groups.google.com/d/msg/leo-editor/muIwfxnxIEA/fza2IvUl1qkJ
All unit tests pass, as do a few hand tests, but more testing is needed.
Please report any problems immediately. Thanks.
Edward
--
Thank you. That was exactly what I was looking for. Very helpful.
I had a little trouble getting the shortcut on my (Windows) desktop
configured - the command-line options go outside the quotation marks
Target: C:\Python34\pythonw.exe C:\Program Files
(x86)\Leo-5.0-final\launchLeo.py
On Tue, Mar 10, 2015 at 11:28 AM, Michael S. msave...@gmail.com wrote:
Is it possible to configure LEO to automatically reopen the outlines that
were open when it was last closed? Like the continue where I left off or
show my windows and tabs from last time option available in web browsers?
On Friday, March 6, 2015 at 1:33:54 PM UTC-8, Edward K. Ream wrote:
I haven't experienced this exactly, but I have noticed that doing
Alt-tab, Alt-tab does not seem always to put focus in Leo's window in such
a way that key bindings are in effect.
I haven't noticed a problem with
On Tue, 10 Mar 2015 10:01:31 -0700 (PDT)
Edward K. Ream edream...@gmail.com wrote:
This rev changes only one line: at.writeVersion5 is now always True.
However, this affects anyone who still uses @shadow. Please report
any problems immediately.
I assume this doesn't break reading of old
Hi,
I was wondering what the best way is to bind more than one command to a
keyboard shortcut.
For example, I'd like Ctrl-q to not be quit, but to run both
gui-menu-toggle
gui-minibuffer-toggle
I can see how this would be done with a plugin, but there is likely a
simpler way.
-Ben
--
You
On Tue, 10 Mar 2015 11:35:33 -0500
Edward K. Ream edream...@gmail.com wrote:
On Tue, Mar 10, 2015 at 11:28 AM, Michael S. msave...@gmail.com
wrote:
Is it possible to configure LEO to automatically reopen the
outlines that were open when it was last closed? Like the
continue where I
This rev changes only one line: at.writeVersion5 is now always True.
However, this affects anyone who still uses @shadow. Please report any
problems immediately.
I'll wait a day or so before eliminating the at.writeVersion5 ivar entirely.
Edward
--
You received this message because you are
I use LEO at work to keep track of several topics and always have the same
set of outlines open - TODO list, ProjectX, ProjectY, etc.
Is it possible to configure LEO to automatically reopen the outlines that
were open when it was last closed? Like the continue where I left off or
show my
This rev completes the grand collapse in complexity needed to truly fix bug
149. This is a big step forward for Leo.
I have been using earlier, mostly equivalent, versions for an hour or more
without problems. Every test I can think of passes. All unit tests pass,
and pylint is happy, and
This switch has been True in leoAtFile.py for several years.
Recent revs simplify the code by removing the switch, and including only
the code that was executed when the switch was True.
All tests pass. Use due caution.
There is one more cleanup to come: removing the writeVersion5. As
START: GIS gobbledegook
QGis somehow fails to read the projection information from a .tif even
though gdalinfo can read it, so I'm thinking there must be an easy way
to create a separate world file for the the .tif
END: GIS gobbledegook
The solution, from Matt Wilkie :-) is here:
The warnings are sometimes given, but not in all cases as before.
I'll fix this within 24 hours in the new code base. There is no going
back. The fix will likely also correct some other buggy edge case.
But now it's time for a break...
Edward
--
You received this message because you are
On Tue, Mar 10, 2015 at 12:20 PM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
This rev changes only one line: at.writeVersion5 is now always True.
However, this affects anyone who still uses @shadow. Please report
any problems immediately.
I assume this doesn't break
18 matches
Mail list logo
