zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: coloring a substitution
Date: Fri, 11 Nov 2022 14:24:48 -0800	[thread overview]
Message-ID: <6042df79-449b-93fc-0d2a-dc990b552c70@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMqjXp6SCwD9o0JwCZUbcpjAayB7zstTib88UHjQ4PqB1A@mail.gmail.com>


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?  
I understand the '$~' now so that's accepted.  As I now have it:

NEW:
     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 ; # Do nothing, we have a match.
     else cc[$aa]=    # Kill the line, it does not match.
     fi
OLD:
     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 ; # Do nothing, we have a match.
     else cc[$aa]=    # Kill the line, it does not match.
     fi


> If this works, consider using more traditional names for these cases:
>
> - case-insensitive partial
> - case-insensitive full
> - case-sensitive partial
> - case-sensitive full

I'm having fun experimenting with these terms and no one but me will 
ever  read them so I amuse myself.  I like 'exact'.  'broad' is 
useless.  Yeah, 'full' and 'partial' are more standard and perfectly 
clear. Tx.




  reply	other threads:[~2022-11-11 22:25 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 [this message]
2022-11-11 22:39         ` Roman Perepelitsa
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=6042df79-449b-93fc-0d2a-dc990b552c70@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).