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: Fri, 11 Nov 2022 07:00:36 -0800	[thread overview]
Message-ID: <6a92000c-dee5-a1e3-a77f-6a4697a66ab1@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7avB4GygP-zVXQEe0N+PyzYK1CC1+XfzOUmg77w3OW-CQ@mail.gmail.com>


On 2022-11-10 15:27, Bart Schaefer wrote:
> On Thu, Nov 10, 2022 at 3:07 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>> Yabut MBEGIN and MEND are showing values that are never explicitly set,
>> they are showing some internal workings surely?
> They are set by the (#m) operator in ${cc//(#m).../...} ... try
> looking those names up in the manual page, hmm?
If I ever cross paths with them again, then yeah.  Worth noting tho is 
that one might actually search for 'MBEGIN' on the internet or even as a 
raw text search in the manual and find something.  As I'm always 
whining, with most of zsh syntax issues that's impossible you have to 
already know the 'name of the family' of the sort of syntactical element 
that you are looking for.  Is it a glob expansion or a parameter flag or 
a pattern match or ... what?  You guys won't sympathize.  Mind, this 
problem is sorta unavoidable since the syntax is so terse.    What I 
wouldn't give for a glossary or a sort of overview of zsh syntactical 
elements  '(#i)' -- so I've learned -- is a regex not a glob not a 
pattern match not any other sort of animal.  Knowing that it's a regex, 
I know where to look for information. but '/**/' is a glob and '(N)' is 
a glob qualifier. Can't learn it from the inside out, only from the 
outside in.  But my little immediate problems are always from the inside 
out.  Slowly but surely tho.
>


  reply	other threads:[~2022-11-11 15:01 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 [this message]
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=6a92000c-dee5-a1e3-a77f-6a4697a66ab1@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).