zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@totalise.co.uk>
To: Akim Demaille <akim@epita.fr>
Cc: zsh-workers@sunsite.dk, ab@purdue.edu, bug-autoconf@gnu.org
Subject: Re: Zsh 3 and ${1+"$@"} (Was: [GNU Autoconf 2.53] testsuite.log: 126 failures)
Date: Tue, 9 Apr 2002 12:45:26 +0100	[thread overview]
Message-ID: <20020409114526.GA30136@logica.com> (raw)
In-Reply-To: <mv44rilxhzo.fsf@nostromo.lrde.epita.fr>

On Tue, Apr 09, 2002 at 12:51:23PM +0200, Akim Demaille wrote:
> 
> | > We (Autoconf) have a big problem with Zsh 3.0.8.  You know it is
> | > shipped on Darwin as /bin/sh.  But this version does not understand
> | > ${1+"$@"} properly.  We use this instead of "$@" to work around a bug
> | > which still exists today in many many constructors' /bin/sh, so we
> | > can't departure from it.

One idea would be if you can use a global alias, e.g.:
  [ x$ZSH_VERSION != x ] && alias -g '${1:"$@"}'='$=@'

Is the ${1+"$@"} always used as a word on its own? The rhs of the alias
may have to be something different - I didn't entirely understand the
problem but you'd have the full flexibility of zsh 3.0.8 expansions so
I'd be suprised if it couldn't be made to work.

> Finally, one question: do you know if Apple plans to continue with Zsh
> 3?  Why did they stick to it?

I think they plan to switch to bash. Not that that helps you much because
Apple's running older versions of Mac OS X will continue to exist for a
while beyond that.

I don't know why they stuck with zsh 4. Perhaps all the shell functions
in zsh 4 scared them off. Solaris also continues with zsh 3 but there
it is only installed as /usr/bin/zsh.

Oliver

-- 

This e-mail and any attachment is for authorised use by the intended recipient(s) only.  It may contain proprietary material, confidential information and/or be subject to legal privilege.  It should not be copied, disclosed to, retained or used by, any other party.  If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender.  Thank you.


  parent reply	other threads:[~2002-04-09 11:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200204081534.g38FYlY0058635@epicenter.eas.purdue.edu>
2002-04-09  9:45 ` Akim Demaille
2002-04-09 10:35   ` Peter Stephenson
2002-04-09 10:51     ` Akim Demaille
2002-04-09 11:05       ` Peter Stephenson
2002-04-09 11:18       ` Bart Schaefer
2002-04-09 11:45       ` Oliver Kiddle [this message]
2002-04-09 11:59         ` Peter Stephenson
2002-04-10 15:52           ` Akim Demaille
2002-04-10 15:54             ` A Braunsdorf
2002-04-10 17:33               ` Akim Demaille
2002-04-10 20:41                 ` A Braunsdorf
2002-04-10 17:09             ` Paul Eggert
2002-04-10 17:32               ` Akim Demaille
2002-04-09 11:30     ` Peter Stephenson
2002-04-09 16:34       ` Bart Schaefer
2002-04-09 16:45         ` Peter Stephenson
2002-04-09 18:09           ` Bart Schaefer

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=20020409114526.GA30136@logica.com \
    --to=okiddle@totalise.co.uk \
    --cc=ab@purdue.edu \
    --cc=akim@epita.fr \
    --cc=bug-autoconf@gnu.org \
    --cc=zsh-workers@sunsite.dk \
    /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).