why is it necessary to have a <TAB> before the email keyword in the [user] section? Other keywords work with whitespace. If not, one get the error message: fatal: bad config file line 2 in /home/guy-kde/.gitconfig
threads / discuss / 26724
a problem with the gitconfig file for user.email
Subject: a problem with the gitconfig file for user.email
Re: a problem with the gitconfig file for user.email
Guy Maurel <guy-kde@maurel.de> writes:
> why is it necessary to have a <TAB> before the email keyword in the [user] > section?
It isn't. I've just checked with email right at the beginning of the line, without tab or space, and it works (with the latest git.git).
> If not, one get the error message: > fatal: bad config file line 2 in /home/guy-kde/.gitconfig
Please, give a short and reproducible senario (eg. the full content of .gitconfig, and the command you've typed to get this).
-- Matthieu Moy http://www-verimag.imag.fr/~moy/
Re: a problem with the gitconfig file for user.email
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
Show 13 quoted lines
> Guy Maurel <guy-kde@maurel.de> writes: > >> why is it necessary to have a <TAB> before the email keyword in the [user] >> section? > > It isn't. I've just checked with email right at the beginning of the > line, without tab or space, and it works (with the latest git.git). > >> If not, one get the error message: >> fatal: bad config file line 2 in /home/guy-kde/.gitconfig > > Please, give a short and reproducible senario (eg. the full content of > .gitconfig, and the command you've typed to get this).
Good suggestion. I suspect this is some third party programs or hooks that are trying to hand parse the config file. In the distant past, some of our perl based Porcelains may have done so but I think these days everything we ship should be reading from "git config" output or calling git_config() from C.
Re: a problem with the gitconfig file for user.email
Hello!
Thanks for helping, but... On Monday, March 14, 2011 12:01:38 AM Junio C Hamano wrote:
Show 13 quoted lines
> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes: > > Guy Maurel <guy-kde@maurel.de> writes: > >> why is it necessary to have a <TAB> before the email keyword in the > >> [user] section? > > > > It isn't. I've just checked with email right at the beginning of the > > line, without tab or space, and it works (with the latest git.git). > > > >> If not, one get the error message: > >> fatal: bad config file line 2 in /home/guy-kde/.gitconfig > > > > Please, give a short and reproducible senario (eg. the full content of > > .gitconfig, and the command you've typed to get this).
I had very little things:
[user]
name = Guy Maurel
email = guy-kde@maurel.de
^^ these are spacesShow 6 quoted lines
> > Good suggestion. I suspect this is some third party programs or hooks > that are trying to hand parse the config file. In the distant past, some > of our perl based Porcelains may have done so but I think these days > everything we ship should be reading from "git config" output or calling > git_config() from C.
I am using kernel 2.6.37-ARCH and git 1.7.4.1-1 64bits But I cannot reproduce the problem *today*. I am sorry, so sorry. I bet your pardon.
As I made a git config --add user.email guy-kde@maurel.de I got a <TAB> before the email keyword, this leads me to my question.
Thanks for helping
-- guy