zsh-users
 help / color / mirror / code / Atom feed
From: "Mark J. Reed" <markjreed@gmail.com>
To: "Lawrence Velázquez" <larryv@zsh.org>
Cc: Joachim Ansorg <mail@bashsupport.com>, zsh-users@zsh.org
Subject: Re: Is ":G" of ${name:s/l/r/:G} actually supported?
Date: Mon, 12 Feb 2024 21:23:36 -0500	[thread overview]
Message-ID: <CAA=-s3xvSpt9iqrDW5RUiGbBNf=9ocN+wHg9xd8SbepcGSB=fA@mail.gmail.com> (raw)
In-Reply-To: <4521f970-04dd-4521-a450-44c365adf625@app.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 3240 bytes --]

>
        In addition to the following operations, the colon modifiers
        described in the section `Modifiers' in the section `History
        Expansion' can be applied: for example, ${i:s/foo/bar/}
        performs string substitution on the expansion of parameter $i.

That's a very helpful snippet that I missed. Thanks. Sorry for the
misinformation.


On Mon, Feb 12, 2024 at 4:52 PM Lawrence Velázquez <larryv@zsh.org> wrote:

> On Mon, Feb 12, 2024, at 12:11 PM, Mark J. Reed wrote:
> > Well, that was a shorter reply than I intended. But you should be able
> > to see that the section you linked (14.1.4 Modifiers) is part of 14.1,
> > History Expansion. Those modifiers don't apply to parameter
> > substitution.
>
> They do.
>
>         % var=foobar
>         % print -- $var:s/o/x
>         fxobar
>
> This is documented in zshexpn(1) under "Modifiers":
>
>         After the optional word designator, you can add a sequence
>         of one or more of the following modifiers, each preceded
>         by a `:'.  These modifiers also work on the result of
>         _filename generation_ and _parameter expansion_, except
>         where noted.
>
> and "PARAMETER EXPANSION":
>
>         In addition to the following operations, the colon modifiers
>         described in the section `Modifiers' in the section `History
>         Expansion' can be applied: for example, ${i:s/foo/bar/}
>         performs string substitution on the expansion of parameter $i.
>
>
> > For doing replacements with parameter expansion, you can just use the
> > slash modifier. One / replaces the first occurrence, two //s does all
> > of them:
> >
> >> *$ value=/dir/subdir/file.csv*
> >> *$ echo ${value//dir/_G}*
> >> */_G/sub_G/file.csv*
> >
> > That's not a zsh-specific feature; ksh and bash have it as well. Zsh
> > likely has a different mechanism to accomplish the same thing, but I've
> > not needed it so am not familiar with it.
>
> The :s and :gs history modifiers are similar but not exactly so.
> Among other things, they perform literal searches by default, allow
> referring to the matched text with "&", and apply nested expansions
> differently.
>
>
> >> On Mon, Feb 12, 2024 at 9:19 AM Joachim Ansorg <mail@bashsupport.com>
> wrote:
> >>> Hi,
> >>> I was reading about modifiers on page
> >>> https://zsh.sourceforge.io/Doc/Release/Expansion.html#Modifiers,
> which says:
> >>>
> >>> >   The forms ‘gs/l/r’ and ‘s/l/r/:G’ perform global substitution,
> i.e. substitute every occurrence of r for l. Note that the g or :G must
> appear in exactly the position shown.
> >>>
> >>> But zsh 5.9 doesn't seem to support this:
> >>>   > value="/dir/subdir/file.csv"
> >>>   > echo ${value:s/dir/_/:G}
> >>>   zsh: unrecognized modifier `G'
>
> It doesn't work on zsh 4.3.11 either, which means it hasn't worked
> for at least 13 years.  (This probably says something about the
> prevalence of applying :s/l/r/:G to parameter expansions.)
>
>
> >>> Is ":G" actually supported or is the documentation outdated here?
>
> I can't say for sure, but this feels like a bug to me.
>
>
> --
> vq
>


-- 
Mark J. Reed <markjreed@gmail.com>

[-- Attachment #2: Type: text/html, Size: 4421 bytes --]

      reply	other threads:[~2024-02-13  2:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 14:19 Joachim Ansorg
2024-02-12 17:02 ` Mark J. Reed
2024-02-12 17:11   ` Mark J. Reed
2024-02-12 21:50     ` Lawrence Velázquez
2024-02-13  2:23       ` Mark J. Reed [this message]

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='CAA=-s3xvSpt9iqrDW5RUiGbBNf=9ocN+wHg9xd8SbepcGSB=fA@mail.gmail.com' \
    --to=markjreed@gmail.com \
    --cc=larryv@zsh.org \
    --cc=mail@bashsupport.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).