From: "SZEDER Gábor" <szeder.dev@gmail•com>
To: git@vger•kernel.org
Subject: bogus config file vs. 'git config --edit'
Date: Fri, 27 Dec 2019 12:04:31 +0100 [thread overview]
Message-ID: <20191227110431.GC32750@szeder.dev> (raw)
Let's suppose I somehow ended up with a bogus config file:
$ tail -n2 .git/config
[section]
foo bar baz
and now I try to rectify the situation, but I know that poking around
in the .git directory is a no-no, so instead of 'vim .git/config' I
try:
$ git config --edit
fatal: bad config line 81 in file .git/config
Uh-oh.
Furthermore, if I don't remember quite clearly the finer points of the
syntax of the config file, then I might want to look it up:
$ git help config
fatal: bad config line 81 in file .git/config
I think bith 'git config --edit' and 'git help ...' should just work,
no matter what nonsense might be in the config file, even if they then
launch a different editor or pager than what are set in the
configuration.
next reply other threads:[~2019-12-27 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 11:04 SZEDER Gábor [this message]
2020-01-08 11:57 ` bogus config file vs. 'git config --edit' Jeff King
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=20191227110431.GC32750@szeder.dev \
--to=szeder.dev@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/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