From: Ellenor Bjornsdottir <ellenor@umbrellix.net>
To: Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: Deprecation of egrep
Date: Sat, 10 Sep 2022 17:26:51 +0000 [thread overview]
Message-ID: <C59B850E-07CF-4E31-A1A2-BA431A9155BA@umbrellix.net> (raw)
In-Reply-To: <CACeGjnWywCnAkuyg33Bny2qaFFi85YoxQiGhjsot+Qrfsd=pEQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
grep from which system? GNU? `egrep` would appear to be a GNU extension, mimicked by some other UNIXes like FreeBSD. "Releases of grep" as a thing separate from the OS is a concept foreign to me, other than GNU.
I am not from zsh-land (though I do use it as my login shell), so I doubt I've a say here, but I'd suggest this looks right. I looked at the SUSv2 grep manpage and this will perform as expected if one's grep complies with SUSv2. (For the count, that's a very old version of POSIX.)
On 10 September 2022 16:04:49 UTC, Vin Shelton <acs@alumni.princeton.edu> wrote:
>Greetings!
>
>The latest release of grep officially deprecates egrep in favor of "grep
>-E". In the build process, we have handled this in our autoconf script,
>but egrep persists in our test scripts, causing failures. Changing all
>occurrences of "egrep" to "grep -E" in our test scripts will fix this. How
>do we want to handle this?
>
>Regards,
> Vin Shelton
>
>--
>
>*Never for money, always for love*
--
Ellenor Bjornsdottir (she)
sysadmin umbrellix.net
[-- Attachment #2: Type: text/html, Size: 1960 bytes --]
next prev parent reply other threads:[~2022-09-10 17:32 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 [this message]
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
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=C59B850E-07CF-4E31-A1A2-BA431A9155BA@umbrellix.net \
--to=ellenor@umbrellix.net \
--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).