2008/6/4 Jeff King <peff@xxxxxxxx>: > On Wed, Jun 04, 2008 at 08:52:14PM +0200, Jean-Baptiste Quenot wrote: > >> Ideally I'd like to feed this list of commits to tig, so that I can >> watch the commit diff and summary easily and switch from one commit to >> another. But tig only behaves as a pager, and does not help for this. > > I think there are two issues here, but both are solvable: > > 1. You want to see _just_ these commits, but not the whole ancestry > chain. In that case, you want to use --no-walk. E.g.: > > tig --no-walk commit1 commit2 ... > > Though it seems there are a few display artifacts. If I do > > tig --no-walk tig-0.1 tig-0.2 > > I get the 2 commits I expect, but also two "extra" blank > commits at the bottom. I confirm there are extra blank lines at the bottom. As many as real commit lines. > 2. tig works like a pager when stdin is not a tty. You can work > around this by using xargs to give the commits to it on the > command line, and then redirect stdin from the tty. > > ... | xargs sh -c 'tig --no-walk "$@" </dev/tty' Thanks for the suggestion. However, my list of commits is too long, the shell errors out with "tig: command too long". I'd like to feed tig with a list of commits from stdin, or from a file. Something like: ... | tig --no-walk -F - Which means: take the list of revisions from specified file, or here - for stdin, a la grep. Cheers, -- Jean-Baptiste Quenot http://jbq.caraldi.com/ -- 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
