From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: coloring substitution seems to eat next line.
Date: Sat, 12 Nov 2022 06:03:12 -0800 [thread overview]
Message-ID: <3a10f310-3ee8-d3b4-f6db-7fdb18b81b1f@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7YBC-eY8B=KDg0K2ZcmZiRuDhYP9WWWq21feiPimg0w1g@mail.gmail.com>
On 2022-11-11 20:24, Bart Schaefer wrote:
> I've never heard the term "glossary" applied to something like that.
True, as I muse I expand the idea from a glossary to a primer to a grammar.
> This is a glossary:
> https://homepages.uc.edu/~thomam/Intro_Unix_Text/Glossary.html
That looks really good, I'm going to scan it end to end. Even if it
was nothing more, something like that focused on zsh -- or I guess just
'shell' -- terminology would be invaluable to someone like me. Probably
was something like that at one time but its fallen by the wayside since,
as I said, raw beginners are now so rare. Really, how many people at my
level are there now? I just decided to dive in at the deep end and
learn to swim by not drowning. Inside out -- solve one problem at a
time, and hope that the grammar would reveal itself eventually. Nope,
the grammar is too terse, too powerful. Latin and Greek are 'C' by
comparison.
> 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.)
Nope, we already have 'the whole book' that's just the thing, I want the
language to be able to read the whole book and understand it. Peter's
'From Bash to Z Shell' was good except that it discussed Bash as much as
Zsh so it confused and diluted as much as it clarified and explained.
> Indeed, search engine text indexing is lousy at short strings and punctuation.
And that's the unavoidable dilemma. Zsh uses one or two characters as
syntactic entities and those same characters might have three or four
meanings in different contexts so the whole paradigm of the google
search is just useless. Nope, hafta read the book. But manuals are not
even designed to be helpful they are repositories of information that
you consult when you know what you are looking for. The right book will
have a glossary in it, helpful hints, anatomy lessons, and a 'phrase
book' -- even if you can't speak German, you can learn to order a beer.
Build up from simple examples. Mean time, my only salvation is asking
you guys for help -- which I always get :-)
next prev parent reply other threads:[~2022-11-12 14:04 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 [this message]
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=3a10f310-3ee8-d3b4-f6db-7fdb18b81b1f@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).