zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: coloring substitution seems to eat next line.
Date: Mon, 14 Nov 2022 09:08:30 -0800	[thread overview]
Message-ID: <77692192-70b3-8a6a-fd01-d5f8b37f59b2@eastlink.ca> (raw)
In-Reply-To: <bfe01c66-e93e-9d25-0d9d-ca3278b3b996@eastlink.ca>

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


On 2022-11-13 07:09, Ray Andrews wrote:
> Roman:
>
>             cc=( ${(M)cc:#*$~zsh_case${filter}*} )
>
> I've been applying that in some other functions but I need a variation 
> that will erase non-matching lines but leave them as blanks so that 
> array indexes do not change.  Reason being that a subsequent merge 
> with another array will happen and indexes must mesh.  I'm doing it 
> right now by using a dummy string as replacement for a non-match and 
> then combining the arrays and then deleting the dummies but that's 
> obviously clumsy.

Stéphane Chazelas 
<https://unix.stackexchange.com/users/22565/st%c3%a9phane-chazelas> over 
at StackExchange offers this:

         cc=( "${cc[@]/#%^*$~zsh_case${filter}*}" )

... and it seems to do exactly what I want.  I understand the negation 
and the way the '[@]' and the outer quotes protect the length of the 
array, now I just need to understand the '#%' anchors -- but they are 
essential.


>
>
>

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

  parent reply	other threads:[~2022-11-14 17:09 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  0:43 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 [this message]
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
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=77692192-70b3-8a6a-fd01-d5f8b37f59b2@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).