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

Re: [PATCH] Make tig call the correct git config command

From
MMMikael Magnusson <mikachu@gmail.com>
Date
Feb 8, 2009, 07:49 UTC
Message-ID
<237967ef0902072349t784e1519m3561ef02545a72de@mail.gmail.com>
In-Reply-To
<237967ef0902072346x4537f70dua37ba897fac99361@mail.gmail.com>

As it turns out I'm an idiot, that's just the configure help message. Rerunning autoconf + configure in fact generates a completely correct commandline. Sorry about the noise.

2009/2/8 Mikael Magnusson <mikachu@gmail.com>:
Show 44 quoted lines
> 2009/2/7 Mikael Magnusson <mikachu@gmail.com>:
>> 2009/2/5 Jonas Fonseca <fonseca@diku.dk>:
>>> Hello,
>>>
>>> Here is a much needed update fixing multiple regressions from the
>>> introduction of the IO API in 0.13. Among improvements is the much
>>> requested ability to restore the position in the stage view when staging
>>> diff hunks. Also noteworthy is the many optimizations of the screen
>>> updating to make it work better across slow links. Finally, beware that
>>> a handful of incompatibilities can cause problems.
>>
>> I'm having a problem with tig taking 2 seconds to start up, which
>> seems to be related to the 'typo checking' feature of git. After
>> figuring out how to stop strace from helpfully saying
>> write(2, "WARNING: You called a Git program"..., 137) = 137
>> I got this (with -s 100):
>> [pid 29708] write(2, "WARNING: You called a Git program named 'git
>> config', which does not exist.\nContinuing under the assu"..., 137) =
>> 137
>> [pid 29708] write(2, "in 2.0 seconds automatically...\n"..., 32) = 32
>>
>> The output however also contains lots of git config strings, which is
>> confusing. Is tig running git config twice and failing one of the
>> times? (Running git config from the cmdline works fine).
>
> Turns out it was as simple as this:
>
> diff --git a/configure.ac b/configure.ac
> index b179389..bdea8de 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -28,7 +28,7 @@ AC_MSG_CHECKING([which config
>  GIT_CONFIG="repo-config"
>  git config --list >/dev/null && GIT_CONFIG="config"
>  AC_MSG_RESULT([$GIT_CONFIG])
> -AC_DEFINE_UNQUOTED(GIT_CONFIG,"$GIT_CONFIG",[git config subcommand])
> +AC_DEFINE_UNQUOTED(GIT_CONFIG,"$GIT_CONFIG",[config subcommand])
>
>  AC_CHECK_PROGS(ASCIIDOC, [asciidoc false])
>  AC_CHECK_PROGS(XMLTO, [xmlto false])
>
> --
> Mikael Magnusson
>
-- 
Mikael Magnusson
Previous: Mikael MagnussonNext: Jonas Fonseca
Message 2 of 5 in “Make tig call the correct git config command”
  1. Make tig call the correct git config commandMikael Magnusson, Feb 8, 2009
  2. Mikael MagnussonFeb 8, 2009
  3. Jonas FonsecaFeb 8, 2009
  4. Kris ShannonFeb 18, 2009
  5. Jonas FonsecaFeb 18, 2009

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.