If you want to find all commits where the commit message contains a given word, use $ git log –grep=word If you want to find all commits where “word” was added or removed in the file contents (to be more exact: where the number of occurrences of “word” changed), i.e., search the commit contents, use … Read more
Do the following: grep -Rnw ‘/path/to/somewhere/’ -e ‘pattern’ -r or -R is recursive ; use -R to search entirely -n is line number, and -w stands for match the whole word. -l (lower-case L) can be added to just give the file name of matching files. -e is the pattern used during the search Along … Read more
Try a character class instead echo “$STRING” | egrep ‘[*]’
find / -type f -name filename.ext -exec grep -l ‘lookingfor’ {} + Using a + to terminate the command is more efficient than \; because find sends a whole batch of files to grep instead of sending them one by one. This avoids a fork/exec for every single file which is found. A while ago … Read more
Default GNU grep behavior is to use a slightly flavorful variant on POSIX basic regular expressions, with a similarly tweaked species of POSIX extended regular expressions for egrep (usually an alias for grep -E). POSIX ERE is what PHP ereg() uses. GNU grep also claims to support grep -P for PCRE, by the way. So … Read more
You could use grep -o then pipe through wc -l: $ echo “123 123 123” | grep -o 123 | wc -l 3
The regular expression to match the end of the line is $, not \n (since grep works a line at a time, it ignores the newlines between lines). grep -c ‘^$’ myfile.txt
Try: nonascii() { LANG=C grep –color=always ‘[^ -~]\+’; } Which can be used like: printf ‘ŨTF8\n’ | nonascii Within [] ^ means “not”. So [^ -~] means characters not between space and ~. So excluding control chars, this matches non ASCII characters, and is a more portable though slightly less accurate version of [^\x00-\x7f] below. … Read more
Awk is the tool that the guys who invented grep, shell, etc. invented to do general text manipulation jobs like this so not sure why you’d want to try to avoid it. In case brevity is what you’re looking for, here’s the GNU awk one-liner to do just what you asked for: awk ‘NR==FNR{a[$0];next} {for(s … Read more
try grep YOUR_PATTERN_AND_OPTION YOUR_PATH | less or grep YOUR_PATTERN_AND_OPTION YOUR_PATH | more