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
See uniq -c. You’ll want to pull out the bit you want, sort the result, pipe thru uniq, sort the output. Something like this maybe: egrep ‘\.[0-9]+:’ output.txt | sort | uniq -c | sort -nr Clarification: I’ve used grep here because it’s not clear what your output.txt format looks like, but you’ll want to … Read more
This happens because grep interprets — as an option instead of a text to look for. Instead, use –: grep — “—” your_file This way, you tell grep that the rest is not a command line option. Other options: use grep -e (see Kent’s solution, as I added it when he had already posted it … Read more
Neither standard nor extended regular expressions support the look behind. Use Perl compatible regexes: grep -P ‘(?<!\\)xxx’ test.tex
This is because you are using the hyphen within other characters, so that grep understands it as a range, which happens to be invalid. You are basically doing grep “[\-‘]” file This is interpreted by grep as you providing a range of characters to be checked on, like for example grep “[a-z]” file. But the … Read more
If the lines are all unique you could grep the lines you want to remove into a file, and then use that file to remove the lines from the original, e.g. grep -C 2 “line I don’t want” < A.txt > B.txt grep -f B.txt A.txt
Either of the these will do: grep -v “def” input_file | grep “abc” or grep “abc” input_file | grep -v “def” The following will also preserve coloring if you only want to see the output on stdout: grep –color=always “abc” input_file | grep -v “def” The -v option (stands for “invert match”) tells grep to … Read more
if echo “$long_str” | grep -q “$shrt_str”;then echo “found” fi or echo “$long_str” | grep -q “$shrt_str” && echo “found” || echo “not found” But since you are using bash shell, then use shell internals. No need to call external commands shrt_str=”guide” case “$long_str” in *”$shrt_str”* ) echo “Found”;; * ) echo “Not found”;; esac
The actual answer to this question is to add || true to the end of the command, e.g.: echo thing | grep x || true This will still output a 0 return code.
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