On Sun, Feb 8, 2009 at 12:06, Jeff King <peff@xxxxxxxx> wrote: > On Sun, Feb 08, 2009 at 11:55:55AM +0100, Jonas Fonseca wrote: > >> On Sun, Feb 8, 2009 at 11:47, Jonas Fonseca <fonseca@xxxxxxx> wrote: >> > One problem it does not yet handle is the >> > cut'n'paste within the same file where the deleted line ends up in a >> > different hunk. >> >> Hmm, this is trivially fixed by passing -M to git blame so maybe that >> should just be the default for tig. > > Yes, I think that is worth doing. It might also be nice to show the > original filename in the blame output (perhaps optionally if it is > different than the original). However, you might want to look at how > "git gui blame" does it. It actually shows _two_ entries for each line: > the origin of the content, and the commit that moved the content into > place. > > I don't know if that is worth doing in tig or not; I think you generally > want to assume a much more constrained screen size (though I have to > admit that I generally maximize my terminal to use "tig blame" anyway -- > 80x25 just doesn't cut it). I wouldn't mind not showing the date and sha1 columns. The sha1 column is mustly there to give a clue about what lines are from the same commit, but that could be done better using the ideas from git-gui. Will look into it when I get some more time ... -- Jonas Fonseca -- To unsubscribe from this list: 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
