zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-user <zsh-users@zsh.org>
Subject: Re: flag z won't cause forced joining?
Date: Fri, 19 Oct 2012 08:38:18 -0700	[thread overview]
Message-ID: <121019083818.ZM3914@torch.brasslantern.com> (raw)
In-Reply-To: <20121019080315.GB6056@localhost.localdomain>

On Oct 19,  4:03pm, Han Pingtian wrote:
}
} I just found that it looks like the z flag won't cause "forced joining"
} which stated in rules 10

Yes, this is a case of the documentation being wrong; it was recently
corrected.  Rule 10 now says:

10. _Forced joining_
     If the `(j)' flag is present, or no `(j)' flag is present but the
     string is to be split as given by rule 11., and joining did not
     take place at step 5., any words in the value are joined together
     using the given string or the first character of $IFS if none.
     Note that the `(F)' flag implicitly supplies a string for joining
     in this manner.

11. _Simple word splitting_
     If one of the `(s)' or `(f)' flags are present, or the `='
     specifier was present (e.g. ${=VAR}), the word is split on
     occurrences of the specified string, or (for = with neither of the
     two flags present) any of the characters in $IFS.

     If no `(s)', `(f)' or `=' was given, but the word is not quoted
     and the option SH_WORD_SPLIT is set, the word is split on
     occurrences of any of the characters in $IFS.  Note this step, too,
     takes place at all levels of a nested substitution.

Note that the reference to rule 17 [the (z) flag] has been removed from
rule 10 (and rule 11 is new).


  reply	other threads:[~2012-10-19 15:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19  8:03 Han Pingtian
2012-10-19 15:38 ` Bart Schaefer [this message]
2012-10-19 23:34   ` 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=121019083818.ZM3914@torch.brasslantern.com \
    --to=schaefer@brasslantern.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).