git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [tig] Feeding specific revisions to tig

From
Jonas Fonseca <jonas.fonseca@gmail.com>
Date
Apr 27, 2009, 10:21 UTC
Message-ID
<2c6b72b30904270321t3d73e2c5o5e3ac8d4b627e5ab@mail.gmail.com>
In-Reply-To
<ae63f8b50904230755p12170753qf3fc273b48afe4d4@mail.gmail.com>
Sorry for the slow reply ...
On Thu, Apr 23, 2009 at 16:55, Jean-Baptiste Quenot <jbq@caraldi.com> wrote:
Show 16 quoted lines
> 2008/8/10 Jonas Fonseca <jonas.fonseca@gmail.com>:
>>> So here is my cut-and-pastable version:
>>>
>>>  tignowalk() {
>>>    tmp=$(mktemp)
>>>    cat >"$tmp"
>>>    TIG_MAIN_CMD="git rev-list --pretty=raw --no-walk --stdin <$tmp" \
>>>      tig </dev/tty
>>>    rm "$tmp"
>>>  }
>>
>> Thanks for the fixed up version.
>
> Restarting this old thread again.  Starting from 0.13 the
> *tignowalk()* hack does not work anymore.  What's the preferred way to
> feed specific revisions using stdin now?
I don't know if it is preferred, but it works. First add a git alias:
[alias]
        tignowalk-helper = !git rev-list --pretty=raw --no-walk --stdin<
Then modify tignowalk by replacing the line calling tig to say:
TIG_MAIN_CMD="git tignowalk-helper $tmp" tig </dev/tty

... and it should work. Maybe more git alias functionality can simplify the hack.

-- 
Jonas Fonseca
Previous: Jean-Baptiste QuenotNext: Jean-Baptiste Quenot
Message 9 of 11 in “[tig] Feeding specific revisions to tig”
  1. Jean-Baptiste QuenotJun 4, 2008
  2. Jeff KingJun 4, 2008
  3. Jean-Baptiste QuenotJun 4, 2008
  4. Jeff KingJun 4, 2008
  5. Jonas FonsecaAug 6, 2008
  6. Jeff KingAug 8, 2008
  7. Jonas FonsecaAug 10, 2008
  8. Jean-Baptiste QuenotApr 23, 2009
  9. Jonas FonsecaApr 27, 2009
  10. Jean-Baptiste QuenotApr 28, 2009
  11. Jean-Baptiste QuenotSep 15, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.