git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Lederhofer <matled@gmx.net>
To: Martin Waitz <tali@admingilde.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Support environment variables in config file
Date: Mon, 4 Jun 2007 07:34:43 +0200	[thread overview]
Message-ID: <20070604053443.GA15148@moooo.ath.cx> (raw)
In-Reply-To: <20070603223727.GA16637@admingilde.org>

Martin Waitz <tali@admingilde.org> wrote:
> Environment variables (e.g. $HOME) can be helpful for the GIT configuration.
> With this change you can use them with the normal shell "$" syntax.
> If you want to insert a plain "$" in a variable, it can be escaped as \$
> or put inside quotes (").

Perhaps we should also allow variable interpolation in double quoted
strings as this is quite common in various languages.

> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index 5868d58..042a354 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -65,17 +65,24 @@ a string, an integer, or a boolean.  Boolean values may be given as yes/no,
>  converting value to the canonical form using '--bool' type specifier;
>  `git-config` will ensure that the output is "true" or "false".
>  
> +You can use the $VARIABLE shell syntax to use environment variables
> +in the configuration file.  All alpha-numeric characters after the
> +leading '`$`' will be interpreted as name of an environment variable
> +and the value of this variable will be used instead.
> +If the variable does not exist it will be treated as an empty string.

We could have a short example here how to concatenate a variable and a
string without a space in between.  I came up with '$FOO""bar' which
is not that obvious imo.

> diff --git a/config.c b/config.c
> index 0614c2b..058c0df 100644
> --- a/config.c
> +++ b/config.c
> @@ -43,12 +43,27 @@ static int get_next_char(void)
>  static char *parse_value(void)
>  {
>  	static char value[1024];
> -	int quote = 0, comment = 0, len = 0, space = 0;
> +	int quote = 0, comment = 0, envvar = -1, len = 0, space = 0;
>  
>  	for (;;) {
>  		int c = get_next_char();
>  		if (len >= sizeof(value))
>  			return NULL;
> +		if ((envvar >= 0) && !isalnum(c)) {

You should allow at least underscores in environment variables too.

> diff --git a/t/t1300-repo-config.sh b/t/t1300-repo-config.sh
> index 3f3fd2d..eb84437 100755
> --- a/t/t1300-repo-config.sh
> +++ b/t/t1300-repo-config.sh
> @@ -513,5 +513,18 @@ git config --list > result
>  
>  test_expect_success 'value continued on next line' 'cmp result expect'
>  
> +cat > .git/config <<\EOF
> +[quoted]
> +	withvar = "$HOME/foo"
> +[unquoted]
> +	withvar = $HOME/foo
> +EOF
> +
> +test_expect_success 'quoted $VAR' \
> +	'test x"\$HOME/foo" = x$(git config quoted.withvar)'
> +
> +test_expect_success 'unquoted $VAR' \
> +	'test x"$HOME/foo" = x$(git config unquoted.withvar)'
> +
>  test_done

If you use the HOME environment variable without setting it yourself
you should place quotes around the $(..) in case there is a space in
$HOME:
    $ ./git-config test.var '$HOME'
    $ export HOME='/tmp/foo bar'
    $ ./git-config test.var
    /tmp/foo bar
    $ test x"$HOME/foo" = x$(./git-config test.var)
    test: 4: bar: unexpected operator
    $ test x"$HOME/foo" = x"$(./git-config test.var)"

  reply	other threads:[~2007-06-04  5:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03 22:37 [PATCH] Support environment variables in config file Martin Waitz
2007-06-04  5:34 ` Matthias Lederhofer [this message]
2007-06-04  7:27   ` Martin Waitz
2007-06-04  8:44     ` Matthias Lederhofer
2007-06-04 15:57     ` Johannes Schindelin
2007-06-04 17:47       ` Martin Waitz
2007-06-04 17:59         ` Johannes Schindelin

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=20070604053443.GA15148@moooo.ath.cx \
    --to=matled@gmx.net \
    --cc=git@vger.kernel.org \
    --cc=tali@admingilde.org \
    /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.
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 NNTP newsgroup(s).