On 03/12/2014 08:04 PM, Junio C Hamano wrote:
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
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,
Junio C Hamano gits...@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
On Wed, Mar 12, 2014 at 08:16:53PM +0100, David Kastrup wrote:
Junio C Hamano gits...@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
Jeff King p...@peff.net writes:
On Wed, Mar 12, 2014 at 08:16:53PM +0100, David Kastrup wrote:
Junio C Hamano gits...@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
On Wed, Mar 12, 2014 at 09:37:41PM +0100, David Kastrup wrote:
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.
Jeff King p...@peff.net writes:
On Wed, Mar 12, 2014 at 09:37:41PM +0100, David Kastrup wrote:
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
7 matches
Mail list logo
