To build this list I used 2 sources. A Study In Scarlet and RATS. I have also added some of my own to the mix and people on this thread have helped out. Edit: After posting this list I contacted the founder of RIPS and as of now this tools searches PHP code for the … Read more
You’ve already got a working answer but just in case you are curious what was wrong with your original approach, the answer is that you need parentheses around your alternation otherwise the (\.|$) is only required if the number is less than 200. ‘\b((25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)(\.|$)){4}\b’ ^ ^
GNU grep can also support positive & negative look-ahead & look-back: For your case, the command would be: echo “Here is a string” | grep -o -P ‘(?<=Here).*(?=string)’ If there are multiple occurrences of Here and string, you can choose whether you want to match from the first Here and last string or match them … Read more
Grep is an awkward tool for this operation. pcregrep which is found in most of the modern Linux systems can be used as pcregrep -M ‘abc.*(\n|.)*efg’ test.txt where -M, –multiline allow patterns to match more than one line There is a newer pcre2grep also. Both are provided by the PCRE project. pcre2grep is available for … Read more
grep ‘potato:’ file.txt | sed ‘s/^.*: //’ grep looks for any line that contains the string potato:, then, for each of these lines, sed replaces (s/// – substitute) any character (.*) from the beginning of the line (^) until the last occurrence of the sequence : (colon followed by space) with the empty string (s/…// … 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
First redirect stderr to stdout — the pipe; then redirect stdout to /dev/null (without changing where stderr is going): command 2>&1 >/dev/null | grep ‘something’ For the details of I/O redirection in all its variety, see the chapter on Redirections in the Bash reference manual. Note that the sequence of I/O redirections is interpreted left-to-right, … Read more
grep -r “texthere” . The first parameter represents the regular expression to search for, while the second one represents the directory that should be searched. In this case, . means the current directory. Note: This works for GNU grep, and on some platforms like Solaris you must specifically use GNU grep as opposed to legacy … Read more
For BSD or GNU grep you can use -B num to set how many lines before the match and -A num for the number of lines after the match. grep -B 3 -A 2 foo README.txt If you want the same number of lines before and after you can use -C num. grep -C 3 … Read more
How do I find all files containing specific text on Linux?