Oh, didn't know about -c. I usually just pipe to wc -l I guess.
Discussion
Loading...
Oh, didn't know about -c. I usually just pipe to wc -l I guess.
-c, -l, -h, -H, and -q are my favorite #grep flags. :D
Huh, that almost became a [Marcel Duchamp] reference. 😅
I just use -v and -E
oh yeah, -E is important. I sometimes use -F for convenience, it's rarely ever faster.
-q is great for use in scripts, like
if some_command |grep -q some_regex; then
It makes the script read very fluidly.
Of course, you should just do if some_command &>/dev/null if the command sends a positive return code on failure, but not all do.
...and bash instead of zsh
...and grep/awk/sed instead of jq
...and firefox instead of chrome
...and the fediverse instead of facebook
Face it... I'm an unpopular-opinion neckbeard level boss. XD
cc: @mirabilos
1 more replies (not shown)
@rl_dane you need "$@"
Really? Even if I'm supplying options like grepc -i foo *.md?
Or should I use IFS=$'\n'?
Seems you were right! I need to skim that part of the manpage again. 😋
@rl_dane yes. And absolutely no, do not touch IFS for this.
"$@" basically means “pass the argv array as-is”.
What happens if you forget the double quotes?
@rl_dane it becomes equivalent to $* without double quotes
Interesting, that feels kinda counter-intuitive, since not quoting things usually keeps them separate, and quoting them lumps them together, like:
~ $ string="hello there"
~ $ for x in $string; do echo $x; done
hello
there
~ $ for x in "$string"; do echo $x; done
hello there
~ $