From: Jonas Fonseca <fonseca@diku.dk>
To: Jonas Fonseca <fonseca@diku.dk>, git@vger.kernel.org
Subject: Re: tig show <commit> not working anymore?
Date: Tue, 21 Sep 2010 08:56:21 -0400 [thread overview]
Message-ID: <AANLkTi=AUiLJJp6JLqWoJufBFDUKa7u3Eg9Az5uGteqM@mail.gmail.com> (raw)
In-Reply-To: <20100920042522.GA21880@bluemoon.alumni.iitm.ac.in>
On Mon, Sep 20, 2010 at 00:25, Kumar Appaiah <a.kumar@alumni.iitm.ac.in> wrote:
> On Sun, Sep 19, 2010 at 02:46:22PM -0400, Jonas Fonseca wrote:
>> You fix is not that far off but to fix the second issue I had to do
>> change the function responsible for expanding %(commit). Anyway,
>> should be fixed in 0.16.1.
>
> Unfortunately, this has introduced another (albeit minor) bug: it
> breaks the tree view in some cases. For example:
>
> git clone git://gitorious.org/taggrepper/taggrepper.git
>
> and run tig there, and press `t'. It always gives me a blank tree.
>
> The cause for this is that view->parent is null when the tree view
> is invoked, but you merely pass !view->parent in the call to
> format_argv in prepare_io.
Oops, I should really finish the tig.c split up branch and introduce a
test suite to catch stuff like this.
> A simple patch to fix this is attached below, but you might have other
> ideas or I might have missed something, or not added sufficient checks
> for the argv vector.
>
> As always, if I have missed something above, please do let me know.
Thanks for the patch and for reporting this. I've fixed this by using
view->prev instead of view->parent. The view->prev tracks the list of
views whereas view->parent tracks parents/child relationships in split
view mode. It was one of the things I refactored not long ago.
--
Jonas Fonseca
prev parent reply other threads:[~2010-09-21 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 12:53 tig show <commit> not working anymore? Kumar Appaiah
2010-09-16 13:46 ` Stefan Naewe
2010-09-16 19:01 ` Kumar Appaiah
2010-09-16 13:47 ` Jonas Fonseca
2010-09-16 18:56 ` Kumar Appaiah
2010-09-16 13:52 ` Michael J Gruber
2010-09-16 13:59 ` Stefan Naewe
2010-09-16 19:03 ` Kumar Appaiah
2010-09-18 5:01 ` Kumar Appaiah
2010-09-18 14:47 ` Jonas Fonseca
2010-09-19 18:46 ` Jonas Fonseca
2010-09-20 4:25 ` Kumar Appaiah
2010-09-21 12:56 ` Jonas Fonseca [this message]
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='AANLkTi=AUiLJJp6JLqWoJufBFDUKa7u3Eg9Az5uGteqM@mail.gmail.com' \
--to=fonseca@diku.dk \
--cc=git@vger.kernel.org \
/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).