AWK If you don’t mind using AWK: awk ‘/yahoo/{y=1;next}y’ data.txt This script has two parts: /yahoo/ { y = 1; next } y The first part states that if we encounter a line with yahoo, we set the variable y=1, and then skip that line (the next command will jump to the next line, thus … Read more
The following sed command will work for you, which does not require any capture groups: sed /000/s/^/#/ Explanation: /000/ matches a line with 000 s perform a substitution on the lines matched above The substitution will insert a pound character (#) at the beginning of the line (^)
This seems to work for me: grep –only-matching –byte-offset –binary –text –perl-regexp “<\x-hex pattern>” <file> Short form: grep -obUaP “<\x-hex pattern>” <file> Example: grep -obUaP “\x01\x02” /bin/grep Output (Cygwin binary): 153: <\x01\x02> 33210: <\x01\x02> 53453: <\x01\x02> So you can grep this again to extract offsets. But don’t forget to use binary mode again.
Test for the end of the line with $ and escape the second . with a backslash so it only matches a period and not any character. grep “.*\.zip$” However ls *.zip is a more natural way to do this if you want to list all the .zip files in the current directory or find … Read more
You are putting quantifier * at the wrong place. Try instead this: – grep ‘^[^\s]*’ text1.txt > text2.txt or, even better: – grep ‘^\S*’ text1.txt > text2.txt \S means match non-whitespace character. And anchor ^ is used to match at the beginning of the line.
git log takes (among other things): -n num to limit the number of commits shown: choose 1 (and if num is 9 or less you can just write -num, hence, -1, for short) –pretty=format:string with directives to change the log output format. The %s directive gets the commit “subject”, which is what you also get … Read more
You can provide several expressions to search for with several -e flags. See also this post. i.e. grep -e expr1 -e expr2
grep by design returns code 1 if the given string was not found. Ansible by design stops execution if the return code is different from 0. Your system is working properly. To prevent Ansible from stopping playbook execution on this error, you can: add ignore_errors: yes parameter to the task use failed_when: parameter with a … Read more
Strangely, the accepted answer printed out the whole line, where I just wanted all the info after the target string. This worked for me: sed -n ‘s/target_string//p’ filename Adapted from this post
This finds all non-text based, binary, and empty files. Edit Solution with only grep (from Mehrdad’s comment): grep -rIL . Original answer This does not require any other tool except find and grep: find . -type f -exec grep -IL . “{}” \; -I tells grep to assume binary files as unmatched -L prints only … Read more