7 ms·
> I'd be surprised if that warning made its way to the mainstream distros. This is the first time I'm hearing about the warning, but I thought I'd run `egrep`
by gatonegro 4y ago
> I'd be surprised if that warning made its way to the mainstream distros.
This is the first time I'm hearing about the warning, but I thought I'd run `egrep` and `fgrep` on my Arch system. Sure enough, both result in warnings: `egrep: warning: egrep/fgrep is obsolescent; using grep -E/-F`
So it's made its way into Arch, at least. Though, like I said, this is the first time I'm hearing about this.
- thayne 4y agoI use arch, and I had an alias for grep to expand to `egrep --color=always` in my interactive shell. I noticed real fast. Fortunately it's an easy fix to `grep -E --color=always`. sidenote: I wish that grep would allow running `grep -E -F`, and have the `-F` flag override the `-E` flag, rather than giving an error about conflicting options, so that I could have an alias like this to make extended regex the default, but allow me to change it with a flag.
- NegativeLatency 4y agoYou could write a little function that does that
- thebeardisred 4y agoFor me, that's the biggest takeaway: Nothing is stopping users from maintaining the behavior they had previously. It's being made explicit that the burden of maintaining that behavior is changing.
- TillE 4y agoYeah, this is a good point. This is basically just GNU saying that those old aliases are not something they want within the scope of grep itself.
- MobiusHorizons 4y agoWhat exactly do you think the burden of _not_ changing a shell script is?