public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu•org>
To: Junio C Hamano <gitster@pobox•com>
Cc: Michael Haggerty <mhagger@alum•mit.edu>,
	git discussion list <git@vger•kernel.org>,
	Fabian <bafain@gmail•com>,
	Quint Guvernator <quintus.public@gmail•com>
Subject: Re: New GSoC microproject ideas
Date: Wed, 12 Mar 2014 20:16:53 +0100	[thread overview]
Message-ID: <87wqfzi5wa.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <xmqq1ty7me6a.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Wed, 12 Mar 2014 12:04:29 -0700")

Junio C Hamano <gitster@pobox•com> writes:

> Here is another, as I seem to have managed to kill another one ;-)
>
> -- >8 --
>
> "VAR=VAL command" is sufficient to run 'command' with environment
> variable VAR set to value VAL without affecting the environment of
> the shell itself, but we cannot do the same with a shell function
> (most notably, "test_must_fail");

No? bash:

dak@lola:/usr/local/tmp/lilypond$ zippo()
> {
> echo $XXX
> echo $XXX
> }
dak@lola:/usr/local/tmp/lilypond$ XXX=8 zippo
8
8


dak@lola:/usr/local/tmp/lilypond$ /bin/dash
$ zippo()
> {
> echo $XXX
> echo $XXX
> }
$ XXX=8 zippo
8
8
$ 

dak@lola:/usr/local/tmp/lilypond$ /bin/ash
$ zippo()
> {
> echo $XXX
> echo $XXX
> }
$ XXX=8 zippo
8
8
$ 


Seems to work just fine with a set of typical shells.

-- 
David Kastrup

  reply	other threads:[~2014-03-12 19:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 11:48 New GSoC microproject ideas Michael Haggerty
2014-03-12 19:04 ` Junio C Hamano
2014-03-12 19:16   ` David Kastrup [this message]
2014-03-12 19:21     ` Jeff King
2014-03-12 20:37       ` David Kastrup
2014-03-12 20:44         ` Jeff King
2014-03-12 21:12           ` David Kastrup
2014-03-13 17:06   ` Michael Haggerty

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=87wqfzi5wa.fsf@fencepost.gnu.org \
    --to=dak@gnu$(echo .)org \
    --cc=bafain@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=mhagger@alum$(echo .)mit.edu \
    --cc=quintus.public@gmail$(echo .)com \
    /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