zsh-workers
 help / color / mirror / code / Atom feed
From: Vin Shelton <acs@alumni.princeton.edu>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: Jun T <takimoto-j@kba.biglobe.ne.jp>,
	"Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: Deprecation of egrep
Date: Mon, 12 Sep 2022 11:27:23 -0400	[thread overview]
Message-ID: <CACeGjnVuwZttU-NUBmE-z4q=h=xh2-rxsoPpVtXFQywYyVCjbg@mail.gmail.com> (raw)
In-Reply-To: <551112370.534185.1662979770948@mail.virginmedia.com>

[-- Attachment #1: Type: text/plain, Size: 564 bytes --]

On Mon, Sep 12, 2022 at 6:54 AM Peter Stephenson <
p.w.stephenson@ntlworld.com> wrote:

>
> 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).


I agree that a zsh-specific solution is best.  FWIW, for clarity I would
remove the 'langs' assignment entirely and put the entire construct on the
'for' statement:

  for LANG in en_{US,GB}.{UTF-,utf}8 en.UTF-8 ${(M)$(locale -a
2>/dev/null):#*.(utf8|UTF-8)} ; do

[-- Attachment #2: Type: text/html, Size: 1454 bytes --]

  reply	other threads:[~2022-09-12 15:33 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
2022-09-12 15:27             ` Vin Shelton [this message]
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='CACeGjnVuwZttU-NUBmE-z4q=h=xh2-rxsoPpVtXFQywYyVCjbg@mail.gmail.com' \
    --to=acs@alumni.princeton.edu \
    --cc=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).