From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: coloring substitution seems to eat next line.
Date: Fri, 11 Nov 2022 20:24:08 -0800 [thread overview]
Message-ID: <CAH+w=7YBC-eY8B=KDg0K2ZcmZiRuDhYP9WWWq21feiPimg0w1g@mail.gmail.com> (raw)
In-Reply-To: <2dd50dc8-cdbc-02e0-0e1e-485718732d0d@eastlink.ca>
On Fri, Nov 11, 2022 at 1:26 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> On 2022-11-11 11:25, Bart Schaefer wrote:
> > Isn't that also true of a glossary?
> Not exactly. The sort of thing I have in mind would be purpose built to
> explain zsh anatomy. It would show you sample code and then 'dissect'
I've never heard the term "glossary" applied to something like that.
This is a glossary:
https://homepages.uc.edu/~thomam/Intro_Unix_Text/Glossary.html
But you seem to want something more like the whole book:
How about https://homepages.uc.edu/~thomam/Intro_Unix_Text/TOC.html
(Or at least everything from Chapter 9 and later.)
> recently the ':#' construction. You won't have much luck googling for
> 'zsh' ':#'
Indeed, search engine text indexing is lousy at short strings and punctuation.
> > Or you could look up "substitution"
> > where you find that for parameters it's usually called "expansion"
>
> Ah! So I was right the first time.
Substitution is a special case of expansion. Globbing is also a
special case of expansion. I was just trying to illustrate that the
index will get you to the general case from the specific.
next prev parent reply other threads:[~2022-11-12 4: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
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 [this message]
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='CAH+w=7YBC-eY8B=KDg0K2ZcmZiRuDhYP9WWWq21feiPimg0w1g@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=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).