Do you need to use ls? You can use find to do the same: find . -maxdepth 1 -perm -111 -type f will return all executable files in the current directory. Remove the -maxdepth flag to traverse all child directories. You could try this terribleness but it might match files that contain strings that look … Read more
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
explainshell helpfully explains your command, and gives an excerpt from man grep: -w, –word-regexp Select only those lines containing matches that form whole words. So just remove -w since that explicitly does what you don’t want: grep -rn ‘/path/to/somewhere/’ -e “pattern”
The exit status of grep doesn’t necessarily indicate an error ; it indicates success or failure. grep defines success as matching 1 or more lines. Failure includes matching zero lines, or some other error that prevented matching from taking place in the first place. -q is used when you don’t care about which lines matched, only … Read more
Try grep -f the_ids.txt huge.csv Additionally, since your patterns seem to be fixed strings, supplying the -F option might speed up grep. -F, –fixed-strings Interpret PATTERN as a list of fixed strings, separated by newlines, any of which is to be matched. (-F is specified by POSIX.)
Just negate the return value. ! grep -P “STATUS: (?!Perfect)” recess.txt
It sounds like you need sed: sed -n ‘/pattern/,/^$/p’ file Don’t print by default (-n). For lines that match /pattern/ up to an empty line /^$/, print.
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
find . -name ‘*.class’ -printf ‘%h\n’ | sort -u From man find: -printf format %h Leading directories of file’s name (all but the last element). If the file name contains no slashes (since it is in the current directory) the %h specifier expands to “.”.