git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Matthieu Moy <git@matthieu-moy.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	rpjday@crashcourse.ca, Git Mailing List <git@vger.kernel.org>
Subject: Re: What means "git config bla ~/"?
Date: Tue, 3 Oct 2017 13:45:52 +0200 (CEST)	[thread overview]
Message-ID: <1964024229.332266.1507031152104.JavaMail.zimbra@matthieu-moy.fr> (raw)
In-Reply-To: <xmqqfub1m6u5.fsf@gitster.mtv.corp.google.com>

"Junio C Hamano" <gitster@pobox.com> writes:

> Jonathan Nieder <jrnieder@gmail.com> writes:
> 
>>> what's with that "git config bla ~/"? is this some config keyword
>>> or something?
>> ...
>>
>> I agree with you that it is less clear than it could be.  Ideas for
>> clarifying it?
> 
> Yeah, if it were
> 
>	git config section.var ~/some/thing
> 
> that would be far clearer than "bla" that what we see is a mere
> placeholder.

Agreed.

> Another obvious option is to remove the parenthetical comment.
> 
> Or "(but you can give values without quoting and let your shell
> expand it)", without a confusing sample command that proved not to
> help very much.

I prefer your "section.var" proposal above. I think people who really understand shell quoting do not need the explanations, and others probably need the example.

While we're there, the formatting is also wrong ('' quoting, while we normally use `` quoting for shell commands).

Sounds like a nice microproject for my students :-). A patch should follow soon.

-- 
Matthieu Moy
https://matthieu-moy.fr/

  reply	other threads:[~2017-10-03 12:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02 10:13 What means "git config bla ~/"? rpjday
2017-10-02 14:06 ` René Scharfe
2017-10-02 17:13 ` Jonathan Nieder
2017-10-03  0:08   ` Junio C Hamano
2017-10-03 11:45     ` Matthieu Moy [this message]
2017-10-04  4:01       ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1964024229.332266.1507031152104.JavaMail.zimbra@matthieu-moy.fr \
    --to=git@matthieu-moy.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=rpjday@crashcourse.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).