zsh-users
 help / color / mirror / code / Atom feed
From: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: zsh-users@zsh.org
Subject: Re: PATCH and more remarks on parameter expansion docs
Date: Thu, 3 Jan 2013 07:28:13 +0800	[thread overview]
Message-ID: <20130102232813.GG2054@localhost.localdomain> (raw)
In-Reply-To: <130102084644.ZM4876@torch.brasslantern.com>

On Wed, Jan 02, 2013 at 08:46:44AM -0800, Bart Schaefer wrote:
> On Jan 2,  4:32pm, Han Pingtian wrote:
> }
> } Thanks your nice patch. But I'm still wondering why not change the
> } statements after "${=spec}" in man page. Or I'm misunderstanding the
> } original statements which has been stating this "splitting before
> } assignment" behavior is only related to "(A)" flag? 
> 
> You mean this?
> 
>      Note that splitting is applied to WORD in the assignment forms of
>      SPEC _before_ the assignment to NAME is performed.  This affects
>      the result of array assignments with the A flag.
Yes, I mean this.

I think it doesn't say this splitting _before_ assignments is only true
when (A) is used. Looks like if (A) wasn't used, splitting will _after_
the assignments:

    % print -l ${=xx::=foo   bar} . $xx . ${(A)=xx::=foo   bar} . $xx
    foo
    bar
    .
    foo   bar
    .
    foo
    bar
    .
    foo
    bar

So I think maybe it should say this splitting before assignments is only
true when (A) is used. The original statements give me the feeling that
this splitting before assignments is peformed in any conditions. Or I am
misunderstanding the statements?

Thanks.
> 
> I must not be understanding what else you think it should say.  Is it
> just that it isn't "... the A flag, among other things"?


  reply	other threads:[~2013-01-02 23:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-30  9:44 Creating A Clean Environment For Autoloaded Functions Russell Harmon
2012-12-30 19:20 ` Bart Schaefer
2012-12-30 21:02   ` Russell Harmon
2012-12-30 22:12     ` Bart Schaefer
2012-12-31 23:30   ` Han Pingtian
2013-01-02  5:15     ` PATCH and more remarks on parameter expansion docs Bart Schaefer
2013-01-02  8:32       ` Han Pingtian
2013-01-02 16:46         ` Bart Schaefer
2013-01-02 23:28           ` Han Pingtian [this message]
2013-01-03 19:42             ` Bart Schaefer
2013-01-03 22:18               ` Han Pingtian

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=20130102232813.GG2054@localhost.localdomain \
    --to=hanpt@linux.vnet.ibm.com \
    --cc=zsh-users@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).