zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Peter Stephenson <Peter.Stephenson@csr.com>
Cc: zsh-workers@zsh.org
Subject: Re: PATCH: expanding parameters like echo/print builtins
Date: Wed, 11 May 2011 19:43:00 +0200	[thread overview]
Message-ID: <BANLkTik5tXk=xUYfc7nkBCawT+sJCcmH6A@mail.gmail.com> (raw)
In-Reply-To: <20110511182657.2d1d99ae@pwslap01u.europe.root.pri>

On 11 May 2011 19:26, Peter Stephenson <Peter.Stephenson@csr.com> wrote:
> On Wed, 11 May 2011 19:19:51 +0200
> Mikael Magnusson <mikachu@gmail.com> wrote:
>> (Should the order
>> parameter expansion flags are applied in be documented somewhere?)
>
> It's documented in *immense* detail in the subsection "Rules" under
> Parameter Expansion, but even the 23 existing rules don't cover
> everything.  Feel free to add another one.  Actually, (V) is covered, at
> rule 15, so maybe you just missed it.

What I meant was that the relation between V and g:: isn't documented,
but yeah, I did miss the whole list :). Here's a patch, minus the
renumbering of subsequent items. Any better names than echo-type
expansion? :)

--- a/Doc/Zsh/expn.yo
+++ b/Doc/Zsh/expn.yo
@@ -1305,6 +1305,9 @@ is applied.
 item(tt(12.) em(Prompt evaluation))(
 Any prompt-style formatting from the tt((%)) family of flags is applied.
 )
+item(tt(13.) em(Echo-type expansion))(
+Any expansion from the tt((g)) flag is applied.
+)
 item(tt(13.) em(Quote application))(
 Any quoting or unquoting using tt((q)) and tt((Q)) and related flags
 is applied.


-- 
Mikael Magnusson


  parent reply	other threads:[~2011-05-11 17:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 13:02 Mikael Magnusson
2011-05-11 15:03 ` Bart Schaefer
2011-05-11 15:14   ` Mikael Magnusson
2011-05-11 16:03     ` Bart Schaefer
2011-05-11 16:22       ` Mikael Magnusson
2011-05-11 16:48         ` Bart Schaefer
2011-05-11 17:11           ` Mikael Magnusson
2011-05-11 15:47   ` Oliver Kiddle
2011-05-11 16:21 ` Peter Stephenson
2011-05-11 16:38   ` Mikael Magnusson
2011-05-11 17:07     ` Peter Stephenson
2011-05-11 17:19       ` Mikael Magnusson
2011-05-11 17:26         ` Peter Stephenson
2011-05-11 17:35           ` Mikael Magnusson
2011-05-11 17:43           ` Mikael Magnusson [this message]
2011-05-12 10:10             ` Bart Schaefer
2011-05-12 10:40               ` Mikael Magnusson
2011-05-12 14:04                 ` Bart Schaefer
2011-05-12 15:49                   ` PATCH: Add g:: parameter expansion flag Mikael Magnusson
2011-05-12 19:41                     ` Mikael Magnusson
2011-05-13  8:54                       ` Peter Stephenson
2011-05-13  9:51                         ` Mikael Magnusson
2011-05-13 11:54                           ` Peter Stephenson
2011-05-13 12:38                             ` Mikael Magnusson
2011-05-14 11:41 PATCH: expanding parameters like echo/print builtins Jilles Tjoelker
2011-05-14 18:41 ` 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='BANLkTik5tXk=xUYfc7nkBCawT+sJCcmH6A@mail.gmail.com' \
    --to=mikachu@gmail.com \
    --cc=Peter.Stephenson@csr.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).