zsh-users
 help / color / mirror / code / Atom feed
From: Jim <linux.tech.guy@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>, zsh <zsh-users@zsh.org>
Subject: Re: quoting question
Date: Wed, 13 Sep 2023 06:28:38 -0500	[thread overview]
Message-ID: <CA+rB6GK1iq-=Xc3h8CodZO=tHCMn0KW+xtaQZm2OTsc78FzQgA@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bAU3GJAMzTsaKKFs7S9fh2+Q_8wbqHR4=aU1HJXwXGUQ@mail.gmail.com>

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

On Tue, Sep 12, 2023 at 3:07 PM Bart Schaefer <schaefer@brasslantern.com>
wrote:

> On Tue, Sep 12, 2023 at 11:46 AM Jim <linux.tech.guy@gmail.com> wrote:
> >
> > Zsh quoting at times makes me wonder. Do quoting? Don't do quoting?
> > The following case has me scratching my head.  Can someone explain what
> is
> > going on?
>
> This doesn't directly have to do with quoting, rather it has to do
> with ${param} expansion and brace expansion.  The short answer is you
> should never have unquoted { } inside the ${...}, because the first }
> encountered is usually going to be interpreted as a match to the ${
> and not to any other { in the string.  Where double-quoting gets
> involved is because inside a double-quoted string, none of the pairs
> of { } have been tokenized, so the lexer can't distinguish which of
> the two }} is the actual end of the expansion.
>
>
For the fifth statement:

 print -- "Date and Time:  ${(%):-%D{%Y-%m-%d %H:%M:%S %Z}} Test"

The following works:

print -- "Date and Time:  ${(%):-"%D{%Y-%m-%d %H:%M:%S %Z}"} Test"

Is this the correct interpretation of your statement, or did I somehow put
a bandaid on it.

I appreciate your input.

Thanks and best regards,

Jim

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

  parent reply	other threads:[~2023-09-13 11:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 18:45 Jim
2023-09-12 20:06 ` Bart Schaefer
2023-09-13  2:50   ` Jim
2023-09-13  3:41     ` Bart Schaefer
2023-09-13 15:09       ` Debug zsh (was: Re: quoting question) Pier Paolo Grassi
2023-09-13 15:28         ` Mikael Magnusson
2023-09-13 11:28   ` Jim [this message]
2023-09-13 16:11     ` quoting question Bart Schaefer
2023-09-12 20:07 ` Peter Stephenson
2023-09-12 20:23   ` Bart Schaefer
2023-09-12 20:29     ` Bart Schaefer
2023-09-13  1:56       ` Mikael Magnusson
2023-09-13  8:50         ` Peter Stephenson

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='CA+rB6GK1iq-=Xc3h8CodZO=tHCMn0KW+xtaQZm2OTsc78FzQgA@mail.gmail.com' \
    --to=linux.tech.guy@gmail.com \
    --cc=linuxtechguy@gmail.com \
    --cc=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).