zsh-users
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: coloring a substitution
Date: Fri, 11 Nov 2022 23:39:21 +0100	[thread overview]
Message-ID: <CAN=4vMrxExZjiFd+Bpt+Mu9BiCenHVENQvqBx3As4oDBVg7X=g@mail.gmail.com> (raw)
In-Reply-To: <6042df79-449b-93fc-0d2a-dc990b552c70@eastlink.ca>

On Fri, Nov 11, 2022 at 11:25 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> On 2022-11-09 00:19, Roman Perepelitsa wrote:
> > Try this instead:
> >    if [[ $scope_msg = 'BROAD'                  && $dirname = (#i)*$~1* ]] ||
> >       [[ $scope_msg = 'Case INsensitive TAME' && $dirname = (#i)$~1 ]] ||
> >       [[ $scope_msg = 'Case Sensitive WILD'      && $dirname = *$~1* ]] ||
> >       [[ $scope_msg = 'EXACT'                  && $dirname = $~1 ]]; then
> >
> That's in place Roman, works identically to mine and I'll keep it on
> your say so, but what are the fine points on why your lines are better?

These four cases are {case-sensitive, case-insensitive} x {full,
partial}. Moreover, the implementation of every case differs only on
these two bits: case insensitivity is always encoded as (#i) and
partial match always as *..*.

The only bizarre thing here is the names of these cases. They don't
reflect the simplicity of the code. The code is in fact so simple that
it's not obvious that it needs any cases other than 'EXACT': $1 can
have (#i) in it to make the match case-insensitive and *..* to make it
partial. It can even have the asterisk only one one side for prefix
and suffix matches.

>      if [[ "$scope_msg" = 'BROAD'                  && $dirname =
> (#i)*$1* ]] \
>      || [[ "$scope_msg" = 'Case INsensitive TAME' && $dirname:u = $1:u ]] \
>      || [[ "$scope_msg" = 'Case Sensitive WILD'      && $dirname =~ $1 ]] \
>      || [[ "$scope_msg" = 'EXACT'                  && $dirname = $1 ]];
> then

Can you similarly describe these four cases, the way I've done in the
first paragraph above? I cannot. All four look uniquely different, so
the inventive names (BROAD, TAME, WILD, EXACT) almost look justified.

Roman.


  reply	other threads:[~2022-11-11 22:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 20:56 Ray Andrews
2022-11-08 21:10 ` Roman Perepelitsa
2022-11-08 23:49   ` Ray Andrews
2022-11-09  0:11     ` Bart Schaefer
2022-11-09  0:32       ` Ray Andrews
2022-11-09  8:19     ` Roman Perepelitsa
2022-11-11 22:24       ` Ray Andrews
2022-11-11 22:39         ` Roman Perepelitsa [this message]
2022-11-12  3:36           ` Ray Andrews

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='CAN=4vMrxExZjiFd+Bpt+Mu9BiCenHVENQvqBx3As4oDBVg7X=g@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.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).