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
To search for commit content (i.e., actual lines of source, as opposed to commit messages and the like), you need to do: git grep <regexp> $(git rev-list –all) git rev-list –all | xargs git grep <expression> will work if you run into an “Argument list too long” error. If you want to limit the search … Read more
grep -r REGEX . Replace . with whatever directory you want to search from.
I once noticed that using -E or multiple -e parameters is faster than using -f. Note that this might not be applicable for your problem as you are searching for 50,000 string in a larger file. However I wanted to show you what can be done and what might be worth testing: Here is what … Read more
What about this: grep -o -c Hello * | awk -F: ‘{if ($2 > 1){print $1}}’
Maybe you want git ls-files which lists the files in the index? (and automatically adjusts for your current directory inside the git work directory)
-d ‘ ‘ means using a single space as delimiter. Since there’re 1 space before 2049 and 2 spaces before 12290, your command get them by -f 2 and -f 3. I recommend using ps aux | awk ‘{print $2}’ to get those pids. Or you can use tr to squeeze those spaces first ps … Read more
To assign the output of a command, use var=$(cmd) (as shellcheck automatically tells you if you paste your script there). #!/bin/bash some_var=$(grep -c “some text” /tmp/somePath) echo “var value is: ${some_var}”
As @Didier said, you can change your delimiter to something other than /: grep -rl $oldstring /path/to/folder | xargs sed -i s@$oldstring@$newstring@g
You don’t need regexps, so grep -F -f file1 file2