Re: git config -> "fatal: bad config file"

git config -> "fatal: bad config file" · David Reitter <hidden> · 2016-06-15
Re: git config -> "fatal: bad config file" · Michael J Gruber <hidden> · 2016-06-15
Re: git config -> "fatal: bad config file" · David Reitter <hidden> · 2016-06-15
Re: git config -> "fatal: bad config file" · Jakub Narebski <hidden> · 2016-06-15
[PATCH] git-config: Parse config files leniently · Michael J Gruber <hidden> · 2016-06-15
Re: [PATCH] git-config: Parse config files leniently · Junio C Hamano <hidden> · 2016-06-15
Re: [PATCH] git-config: Parse config files leniently · Michael J Gruber <hidden> · 2016-06-15

From: David Reitter <hidden>
Date: 2016-06-15 22:47:14

On Aug 14, 2009, at 10:18 AM, Michael J Gruber wrote:

git needs to read the file because the editor could be configured  
there!
The only option would be to make git config -e continue past that  
error.


Syntax errors in .git/config could lead to warnings. Since the file is  
primarily line-oriented anyways (except for groups), recovery should  
be easy.

Also, you could have git-config -e edit a temporary file, check the  
file for errors after editing and then move it to .git/config.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help