From: Jonas Fonseca <fonseca@diku•dk>
To: Jakub Narebski <jnareb@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [ANNOUNCE] tig-0.10
Date: Mon, 17 Mar 2008 11:27:43 +0100 [thread overview]
Message-ID: <20080317102743.GB6830@diku.dk> (raw)
In-Reply-To: <m3r6e9wup2.fsf@localhost.localdomain>
Jakub Narebski <jnareb@gmail•com> wrote Mon, Mar 17, 2008:
> Jonas Fonseca <fonseca@diku•dk> writes:
>
> > A new version of tig is available! It brings many documentation
> > improvements, bug fixes, and some much needed updates to work better
> > with git (e.g. by using --no-color and avoiding to use git-diff).
>
> It seems like 'g', toggle revision graph visualization, doesn't work.
> Checked with
> $ tig log --pretty=oneline --abbrev=8 --abbrev-commit
Well, the revgraph visualization only works for the main view, not the
log view (which has been sort of deprecated).
> > On startup, tig will now attempt to first read a system-wide configuration
> > file before loading the user specific configuration file. Cherry picking
> > from inside tig has been generalized, making it possible to wire
> > external commands, which can access information about the current
> > commit, to a keybinding.
>
> By thw ay, in tig(1), in the "FILES" section, there is
>
> /home/fonseca/etc/tigrc
> System wide configuration file.
>
> Is it a bug in code, or just in documentation.
Oops, embarrasing. I will look into fixing it so that documentation
installed from the tarball will insert the local sysconfdir path.
--
Jonas Fonseca
next prev parent reply other threads:[~2008-03-17 10:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 2:03 [ANNOUNCE] tig-0.10 Jonas Fonseca
2008-03-17 8:25 ` Junio C Hamano
2008-03-17 10:23 ` Jonas Fonseca
2008-03-17 10:49 ` Junio C Hamano
2008-03-17 11:28 ` Jonas Fonseca
2008-03-17 9:45 ` Jakub Narebski
2008-03-17 10:27 ` Jonas Fonseca [this message]
2008-03-19 23:33 ` [ANNOUNCE] tig-0.10.1 Jonas Fonseca
2008-03-20 0:52 ` Junio C Hamano
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=20080317102743.GB6830@diku.dk \
--to=fonseca@diku$(echo .)dk \
--cc=git@vger$(echo .)kernel.org \
--cc=jnareb@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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