git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonas Fonseca <jonas.fonseca@gmail.com>
To: Jean-Baptiste Quenot <jbq@caraldi.com>
Cc: git@vger.kernel.org
Subject: Re: [tig] Feeding specific revisions to tig
Date: Mon, 27 Apr 2009 12:21:05 +0200	[thread overview]
Message-ID: <2c6b72b30904270321t3d73e2c5o5e3ac8d4b627e5ab@mail.gmail.com> (raw)
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:
> 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

  reply	other threads:[~2009-04-27 10:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 18:52 [tig] Feeding specific revisions to tig Jean-Baptiste Quenot
2008-06-04 19:29 ` Jeff King
2008-06-04 20:04   ` Jean-Baptiste Quenot
2008-06-04 23:08     ` Jeff King
2008-08-06 11:06       ` Jonas Fonseca
2008-08-08 21:19         ` Jeff King
2008-08-10  9:16           ` Jonas Fonseca
2009-04-23 14:55             ` Jean-Baptiste Quenot
2009-04-27 10:21               ` Jonas Fonseca [this message]
2009-04-28  8:15                 ` Jean-Baptiste Quenot
2011-09-15 15:10                 ` Jean-Baptiste Quenot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2c6b72b30904270321t3d73e2c5o5e3ac8d4b627e5ab@mail.gmail.com \
    --to=jonas.fonseca@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jbq@caraldi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).