From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Jun T <takimoto-j@kba.biglobe.ne.jp>, zsh-workers@zsh.org
Subject: Re: Deprecation of egrep
Date: Mon, 12 Sep 2022 11:49:30 +0100 (BST) [thread overview]
Message-ID: <551112370.534185.1662979770948@mail.virginmedia.com> (raw)
In-Reply-To: <46F0A32F-93D2-4E67-9C72-2DC924AC21FD@kba.biglobe.ne.jp>
> On 12/09/2022 11:15 Jun T <takimoto-j@kba.biglobe.ne.jp> wrote:
> If we are going to patch each file that uses egrep, we can use
> zsh pattern matching in each of them; for example:
>
> diff --git a/Test/D07multibyte.ztst b/Test/D07multibyte.ztst
> index e2e9a25ef..cde3f2b81 100644
> --- a/Test/D07multibyte.ztst
> +++ b/Test/D07multibyte.ztst
> @@ -6,7 +6,7 @@
> unset -m LC_\*
> mb_ok=
> langs=(en_{US,GB}.{UTF-,utf}8 en.UTF-8
> - $(locale -a 2>/dev/null | egrep 'utf8|UTF-8'))
> + ${(M)$(locale -a 2>/dev/null):#*.(utf8|UTF-8)} )
> for LANG in $langs; do
> if [[ é = ? ]]; then
> mb_ok=1
>
> I don't know which is better.
I tend to agree with Bart that a change like the above is probably best
in the long run. Directly using zsh's own features inline would be
clearer (given the core audience here is zsh experts anyway).
pws
next prev parent reply other threads:[~2022-09-12 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 16:04 Vin Shelton
2022-09-10 17:26 ` Ellenor Bjornsdottir
2022-09-12 5:32 ` Jun T
2022-09-12 7:30 ` Jun T
2022-09-12 9:08 ` Daniel Shahaf
2022-09-12 10:15 ` Jun T
2022-09-12 10:49 ` Peter Stephenson [this message]
2022-09-12 15:27 ` Vin Shelton
2022-09-13 4:33 ` Jun T
2022-09-23 17:14 ` Jun. T
2022-09-11 0:10 ` Bart Schaefer
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=551112370.534185.1662979770948@mail.virginmedia.com \
--to=p.w.stephenson@ntlworld.com \
--cc=takimoto-j@kba.biglobe.ne.jp \
--cc=zsh-workers@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).