From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: coloring substitution seems to eat next line.
Date: Thu, 10 Nov 2022 10:45:44 -0800 [thread overview]
Message-ID: <d0f59044-0dc7-9117-21f5-35904231c6b9@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMoDkfG=SgpLjreoWZhwrhfEucGgeiKoRXB+ZQgi=nHohA@mail.gmail.com>
On 2022-11-10 10:36, Roman Perepelitsa wrote:
> Does that matter? I thought it was one of those situations where the
>> dollar sign is optional.
> It matters if cc is an associative array. Given that you've
> (accidentally) used slice assignment with cc, it cannot be an
> associative array.
Correct. Anyway that's good to know, I think I've only used an
associative array once and not here.
> I've never heard of slice assignment :(
> These two aren't the same:
>
> cc[42]="foo bar"
> cc[42]=(foo bar)
>
> The second is a slice assignment.
Ok, I'll play with that. Sheesh, the things I don't even know that I
don't know. Is there somewhere I can read up on that?
> You can filter beforehand like this:
> cc=(${(M)cc:#*$filter*})
>
> This assumes that $filter doesn't have metacharacters. If it does and
> you want to treat them as such, use $~filter.
Thanks, I'll tinker with that. It will be satisfying to be able to
avoid sed ... come to that I just went back to grep for the filter and
colorization because sed's separation character might just be part of a
directory name. These little things! grep is faster too. But native
code will be best.
>
> Roman.
>
next prev parent reply other threads:[~2022-11-10 18:46 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 [this message]
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
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=d0f59044-0dc7-9117-21f5-35904231c6b9@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).