zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] run-help: ugly workaround for run-help-$X with alias for $X
Date: Mon, 14 Dec 2009 07:50:55 -0800	[thread overview]
Message-ID: <091214075055.ZM8191@torch.brasslantern.com> (raw)
In-Reply-To: <200912141342.nBEDg23i004301@news01.csr.com>

On Dec 14,  1:42pm, Peter Stephenson wrote:
} Subject: Re: [PATCH] run-help: ugly workaround for run-help-$X with alias 
}
} =?iso-8859-1?Q?J=F6rg?= Sommer wrote:
} > Why do you need the unset here?
} 
} It's the same "unset" that was in the original, just moved to a
} position where it's guaranteed always to be executed.

Aside:  I can't find the "var=value command ..." syntax anywhere in
the zsh manual.  I was sure there was some mention of it, but it seems
to be in the category of "things all shells do" that zsh's manual does
not bother to reiterate.

That unset is probably there because older versions of zsh had some
bugs in the implementation of "var=value command ..." particularly in
the case where "command" is a function or builtin.  This stemmed from
zsh's efforts to avoid forking when no external program was involved.

(I have the nagging feeling there are still some cases where the
parameter will intentionally remain set, but I can't recall what.)

However, the versions of zsh that have that problem will choke on the
"always" syntax, so there's no backwards compatibility benefit here.


  reply	other threads:[~2009-12-14 15:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 11:40 Jörg Sommer
2009-12-14 13:42 ` Peter Stephenson
2009-12-14 15:50   ` Bart Schaefer [this message]
2009-12-14 16:38     ` Andrey Borzenkov
2009-12-14 17:01       ` Bart Schaefer
2009-12-16 10:57     ` Peter Stephenson
2009-12-18 13:51       ` Jörg Sommer
  -- strict thread matches above, loose matches on Subject: below --
2009-12-07  0:57 Jörg Sommer
2009-12-10  9:49 ` Peter Stephenson

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=091214075055.ZM8191@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).