Re: The design of Leo's git diff interface

2017-06-15 Thread Edward K. Ream
On Thursday, June 15, 2017 at 12:23:15 PM UTC-5, Edward K. Ream wrote: > > I wonder whether git can deliver (the contents of) blobs by file name and commit. > Well, of course it can: git show HEAD~2:./leo/core/commit_timestamp.json ... > If this output can be piped into Leo we won't need gitpytho

Re: The design of Leo's git diff interface

2017-06-15 Thread Edward K. Ream
On Thursday, June 15, 2017 at 12:13:55 PM UTC-5, Edward K. Ream wrote: > I wonder whether git can deliver (the contents of) blobs by file name and commit. Well, of course it can: git show HEAD~2:./leo/core/commit_timestamp.json produces: { "asctime": "Wed Jun 14 05:08:29 CDT 2017",

Re: The design of Leo's git diff interface

2017-06-15 Thread Edward K. Ream
On Thursday, June 15, 2017 at 11:55:05 AM UTC-5, Edward K. Ream wrote: > I'm going to study the gitk sources (part of the git distro) to see how they work. That may give me ideas for bypassing gitpython. Meh. They are written in tcl and Leo doesn't have an importer for that. For now, using git

The design of Leo's git diff interface

2017-06-15 Thread Edward K. Ream
The actual programming/diffing part of showing git diffs within Leo seems well within reach. However, that's not the most important task at hand. We could imagine adding a git-diff command to Leo. This command would show the outline-oriented diff of the selected @ tree against the last commit.