zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Belaboring substitution syntax
Date: Tue, 15 Nov 2022 18:54:22 -0800	[thread overview]
Message-ID: <0ce205d5-31f9-907a-61bd-1bf5acb37f0f@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7ZWz0cdQLc9kr1cTBun=5TW4=1meSzc8Uf4JBTM9Wa9NQ@mail.gmail.com>


On 2022-11-15 17:49, Bart Schaefer wrote:
> BTW you need to stop thinking of these as "lines" -- line breaks have
> nothing to do with it.
Because I've never had an element that was more than one line I tend to 
say 'lines' but I know abstractly what you're saying.  I'll crash into 
the issue eventually and I'll be ready for it.
> Conversely if you write "${array}" or ${array[*]}" either one with the
> quotes, you get the entire array joined into a single string.
Right, that's quotes doing joining which I expect.
> Quotes ALWAYS protect SOMETHING from expansion or interpretation,
> unless you start throwing other things in there such as eval.  WHAT is
> protected differs:  Double quotes allow ${param} and $(process) and
> $((math)) replacements but protect syntax tokens and glob patterns and
> whitespace; single quotes protect pretty much everything.
Yeah, I get all that.  There are times when I want to protect but not 
join tho and it gets confusing.
> In the specific example in this thread, zsh's default array behavior
> (no_SH_WORD_SPLIT) is sufficient, but if you later enclose that or a
> similar construct in a deeper context, yes, you might be bitten.
I'll stay safe.
> Your trouble is the definition of "nothing."  ${B:#*A*} does that, but
> in your example here, you don't actually want "nothing", you want "the
> empty string" which is still something.
Quite so, rather sloppy of me to say 'nothing', I know better.
> About the only thing your magical operator could remove is putting
> *...* around the pattern to mean "is a substring".
>
Well no, I *define* my operator to do just as I said (except that I 
should have said 'empty string').  All that puzzles me is that it's not 
already available.  Mind, functionality is added as needed so it's 
sufficient to just say that nobody has much wanted such a thing -- which 
is not debatable.  It's a fact on the ground that my operator doesn't 
exist ergo it's not been in demand and that's that.   So long is my 
functionality is achievable the rest is just musing.  Still I'd have 
expected it to be one of the earlier operators because it's the simplest 
case.  Nevermind.




  reply	other threads:[~2022-11-16  2:57 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  0:43 coloring substitution seems to eat next line Ray Andrews
2022-11-10  8:02 ` Roman Perepelitsa
2022-11-10 18:25   ` Ray Andrews
2022-11-10 18:36     ` Roman Perepelitsa
2022-11-10 18:45       ` Ray Andrews
2022-11-10 18:54       ` Bart Schaefer
2022-11-10 19:28         ` Ray Andrews
2022-11-10 20:22           ` Bart Schaefer
2022-11-10 21:42             ` Ray Andrews
2022-11-10 21:51               ` Roman Perepelitsa
2022-11-11 17:24                 ` Ray Andrews
2022-11-10 22:47               ` Bart Schaefer
2022-11-10 23:07                 ` Ray Andrews
2022-11-10 23:27                   ` Bart Schaefer
2022-11-11 15:00                     ` Ray Andrews
2022-11-11 18:15                       ` Bart Schaefer
2022-11-11 18:50                         ` Ray Andrews
2022-11-11 19:25                           ` Bart Schaefer
2022-11-11 21:26                             ` Ray Andrews
2022-11-12  4:24                               ` Bart Schaefer
2022-11-12 14:03                                 ` Ray Andrews
2022-11-13 15:09                                   ` Ray Andrews
2022-11-14 14:12                                     ` Roman Perepelitsa
2022-11-14 17:08                                     ` Ray Andrews
2022-11-14 17:12                                       ` Roman Perepelitsa
2022-11-14 18:58                                         ` Ray Andrews
2022-11-14 20:00                                           ` Bart Schaefer
2022-11-14 23:25                                             ` Ray Andrews
2022-11-15 14:17                                               ` Belaboring substitution syntax Ray Andrews
2022-11-16  1:49                                                 ` Bart Schaefer
2022-11-16  2:54                                                   ` Ray Andrews [this message]
2022-11-16  6:26                                                     ` Bart Schaefer
2022-11-16 14:08                                                       ` Ray Andrews
2022-11-16 14:13                                                         ` Roman Perepelitsa
2022-11-17  2:31                                                           ` Bart Schaefer
2022-11-17  8:59                                                             ` Roman Perepelitsa
2022-11-17 16:02                                                               ` Ray Andrews
2022-11-16 20:46                                                       ` Ray Andrews
2022-11-16 10:32                                                   ` Roman Perepelitsa

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=0ce205d5-31f9-907a-61bd-1bf5acb37f0f@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --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).