From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: coloring substitution seems to eat next line.
Date: Fri, 11 Nov 2022 09:24:47 -0800 [thread overview]
Message-ID: <17005577-0b12-dd36-481f-3db889082f5d@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMpkMC+W7ygcDREM8UtJGqs+3RFCmMF-2CE+d_vn5HAHDg@mail.gmail.com>
On 2022-11-10 13:51, Roman Perepelitsa wrote:
> If you look back, you can find in my answers a way to:
> 1. Remove all elements of an array that don't match a pattern. It has this form:
>
> array=(${(M)array:#pattern})
>
> 2. Perform a replacement in all elements of an array. Like this:
>
> array=(${array//pattern/substitute})
>
Fabulous:
for filter in "$@"; do
cc=( ${(M)cc:#*$~zsh_case${filter}*} )
cc=(
${cc//(#b)($~zsh_case${filter})/$'\e['$color;1m${match[1]}$'\e[0m'} )
done
... no need for a a loop processing each line one at a time. Once the
non-matching lines are removed, the whole array can be colorized in one
gulp. I knew there'd be an elegant way.
> You can save a tremendous amount of time by reading the official guide
> and the reference.
IF you know what you are looking for! I can't look for '(M)' before I
know the thing exists to be looked for.
> Set aside an evening or two and read them from
> start to end.
This mortal would need to devote a year to it. I have tried but one
needs to understand the jargon before it's even intelligible. But yes,
it needs to be learned from the outside in. You experts don't realize
how steep the learning curve is. Oh, for a glossary!
next prev parent reply other threads:[~2022-11-11 17:25 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 [this message]
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
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=17005577-0b12-dd36-481f-3db889082f5d@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).