We are stuck with egrep and fgrep (unless you like beating people)

Re:We are stuck with egrep and fgrep (unless you like beatin... by Beltalowda on Thursday October 13, 2022 @10:07AM (#33191141)

I don't think grep does any argv-stuff; I took a quick look and I don't see it.

As far as I can tell this is the entire maintenance burden:

  $ cat =egrep =fgrep
  #!/bin/sh
  exec grep -E "$@"
  #!/bin/sh
  exec grep -F "$@"

[ Parent | on HN ]

Re:We are stuck with egrep and fgrep (unless you like beatin... by yubiox on Thursday October 13, 2022 @11:30AM (#33192376)

what shell does this?

[ Parent | on HN ]

Re:We are stuck with egrep and fgrep (unless you like beatin... by forgotpwd16 on Thursday October 13, 2022 @11:52AM (#33192696)

Apparently zsh replaces =cmd with cmd's absolute path. TIL.

[ Parent | on HN ]

Re:We are stuck with egrep and fgrep (unless you like beatin... by Beltalowda on Thursday October 13, 2022 @12:39PM (#33193388)

Yes, very useful to bypass aliases if need be, quickly edit a script ("vi =my-script"), etc. I don't think bash has it; you need to use where/whence/which/command/whatever (I can never remember, why are there so many?!)

[ Parent | on HN ]

Re:We are stuck with egrep and fgrep (unless you like beatin... by btdmaster on Thursday October 13, 2022 @02:43PM (#33194828)

Hack: \command instead of command is very unlikely to be aliased, so should work fine.

[ Parent | on HN ]

Re:We are stuck with egrep and fgrep (unless you like beatin... by ykonstant on Friday October 14, 2022 @01:59PM (#33206762)

This is a very useful hack, thanks. Unfortunately, my defensive scripting instincts do not allow me to use it on the "serious" situations.

[ Parent | on HN ]