zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
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, 09 Apr 2002 12:05:30 +0100	[thread overview]
Message-ID: <18488.1018350330@csr.com> (raw)
In-Reply-To: "Akim Demaille"'s message of "09 Apr 2002 12:51:23 +0200." <mv44rilxhzo.fsf@nostromo.lrde.epita.fr>

Akim Demaille wrote:
> | I think the problem you are running across is that with the option
> | SH_WORD_SPLIT set (as it is for sh compatibility), you get this behaviour:
> | 
> | % set 'one two'
> | % for arg in ${1+"$@"}; do echo $arg; done
> | one
> | two
> | 
> | whereas you expect `one two' on the same line.  
> 
> `you' == akim, or == the sh standard?

Both, presumably, although I haven't explicitly followed through the
standard.  (It's kind of irrelevant, since you (akim) are explicitly
trying to work around eccentricities.)

> | This problem is still in
> | zsh 4 --- inside another substitution, either it's splitting all words
> | on spaces, or it's splitting none.
> 
> I'm sure I understand you here, given that Zsh 4 exhibiting the
> behavior I (Akim :) was expecting.

Not for me...

% zsh -f
% setopt shwordsplit
% set 'one word' 'two words'
% for arg in ${1+"$@"}; do echo $arg; done
one
word
two
words
% print $ZSH_VERSION
4.1.0-dev-4

Same in 4.0.  Possibly you tried it without shwordsplit --- remember
it's only set by default if you invoke zsh in sh-compatibility mode.

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

There's a story they're going to switch to bash, but it's difficult to
get information --- we've only ever heard second hand from someone who
knows someone etc. etc...

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 392070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************


  reply	other threads:[~2002-04-09 11:06 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 [this message]
2002-04-09 11:18       ` Bart Schaefer
2002-04-09 11:45       ` Oliver Kiddle
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=18488.1018350330@csr.com \
    --to=pws@csr.com \
    --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).