Jonas Fonseca <fonseca@xxxxxxx> writes:
> The problem is of course to come up with some ascii-art which is both
> readable and dense. Below is my mockup of something not using line
> graphics, however using line graphics it might be possible to get
> something more unambiguos but also more "edgy".
I do not necessarily think an ascii-art is needed, nor an
appropriate way to present it to the curses user. When the user
wants to "view" a commit, you could show from which branch heads
and from which tags the commit is reachable, and perhaps which
tag is the latest among the ones reachable from that commit, as
part of the commit detail information you display on the lower
pane (log/diff view).
I may not be using tig in the way it was intended to, but I
often find it frustrating having to do the following:
- start tig, which shows list of one-line logs. Wonderful.
- browsing around by UP or DOWN and stop at one particular commit
I want to view closely. Press Enter and the screen split
into two and I see what I want to see. Again, wonderful.
- I want to see the neighbouring commits, but UP or DOWN
does not do what I naïvely expect. It scrolls the lower
pane. I say TAB to go up.
- Press UP or DOWN and I can move the highlight to
neighbouring commits. This is wonderful, but the lower
pane does not follow this -- it keeps showing the original
commit, and I have to say ENTER again.
It might make sense to make the log/diff view follow what
happens on the main view when both are on-screen.
-
: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html