From: David Kastrup <dak@gnu.org>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
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 21:37:41 +0100 [thread overview]
Message-ID: <87siqni25m.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20140312192108.GA1601@sigill.intra.peff.net> (Jeff King's message of "Wed, 12 Mar 2014 15:21:08 -0400")
Jeff King <peff@peff.net> writes:
> On Wed, Mar 12, 2014 at 08:16:53PM +0100, David Kastrup wrote:
>
>> 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
>
> Try:
>
> zippo() {
> echo $XXX
> }
> XXX=8 zippo
> zippo
>
> XXX remains set after the first call under dash (but not bash). I
> believe "ash" has the same behavior.
Yes. I would lean towards considering this a bug. But I agree that it
does not help.
--
David Kastrup
next prev parent reply other threads:[~2014-03-12 20:37 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
2014-03-12 19:21 ` Jeff King
2014-03-12 20:37 ` David Kastrup [this message]
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=87siqni25m.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=bafain@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
--cc=quintus.public@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.