On Monday, May 22, 2017 at 11:21:25 AM UTC-5, Edward K. Ream wrote:
>
> On Mon, May 22, 2017 at 10:49 AM, Terry Brown <[email protected]>
> wrote:
>
>> how many changes to
non-curses Leo code has the project required?
> None of any consequence...Most other changes involved improved traces.
See for yourself.
I thought about this on my walk today. Here are some attempts to have git
show us the changes in leo\core since April 18, the day I started work on
this project:
git whatchanged --since="4/18/2017" leo\core >git_log.txt
This works, but alas most entries are for commit_timestamp.json. Stack
overflow contains a discussion about excluding files
<https://stackoverflow.com/questions/39931781/git-diff-stat-exclude-certain-files>
with git filespecs, but I have yet to make that work.
This is much better:
git whatchanged --since="4/19/2017" leo\core\leo*.py >git_log.txt
However, this shows only the commit messages, not the actual diffs. I made
(by hand) the following list of files that have been changed:
leoApp.py
leoAst.py
leoAtFile.py
leoBeautify.py
leoBridge.py
leoCache.py
leoChapters.py
leoColorizer.py
leoCompare.py
leoConfig.py
leoCommands.py
leoExternalFiles.py
leoFileCommands.py
leoFind.py
leoFrame.py
leoGlobals.py
leoGui.py
leoHistory.py
leoImport.py
leoKeys.py
leoMenu.py
leoNodes.py
leoPlugins.py
leoRst.py
leoTangle.py
leoTest.py
leoUndo.py
leoVim.py
That's a surprising number of files, but the important question is whether
there have been any significant changes in *any* of those files. I think
not. I like gitk the best for detailed inspections. Like this:
gitk --since="4/18/2017" leo\core\leoApp.py
Note that the last (bottom) entry shown is the commit *before* 4/18/2017.
This uses gitk to diff all files at once:
gitk --since="4/18/2017" leo\core\leo*.py
I don't recall having any qualms about any of the changes make to Leo's
core for this work, and I think I would have remembered any ;-) I would be
shocked if any changes made to Leo's core caused any problems. Certainly
all unit tests have continued to pass and I have been eating my own dog
food without any problems. Still, I'll give this last set of diffs a
look-see.
Edward
P. S. As a separate issue, I would like to suppress diffs that involve
moving only a block of lines (maybe even only those delimited by Leo's node
sentinels!). It may be possible to determine easily whether the moved block
differs in any *other* way from the original block, but I'm not sure. Imo,
this would be a really nice post-pass to apply to git diff. I've wanted
something like this for a long time...
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.
