R.L. Dane 
🍵 
File this under #shell #functions I should have written years ago:
function grepc {
#Do a grep -c, but skipping files with no results
grep -c "$@" |grep -v ':0$'
}
mirabilosReally? 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?
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
~ $
witch_t *navi@mirabilos @rl_dane
it's easier to think of $@ as an array type to me
if you quote a string, it goes as is, if you don't, it is split
if you quote an array, it goes as is, if you don't, each entry is split
this would feel a lot less "special case-y" if we had proper arrays variables other than arguments... i'm working on it...
it's easier to think of $@ as an array type to me
if you quote a string, it goes as is, if you don't, it is split
if you quote an array, it goes as is, if you don't, each entry is split
this would feel a lot less "special case-y" if we had proper arrays variables other than arguments... i'm working on it...