find and output files content with filtering by filename and specific string

find . -name *.properties -exec /bin/echo {} \; -exec cat {} \; | grep -E 'listen|properties'

-1
By: altern
2014-02-17 02:25:49

These Might Interest You

What Others Think

Sorry, this is a mess. You don't need: -exec /bin/echo {} \; because find has -print find even has -printf if you want to get fancy. Because you're piping ALL the output into grep, you have to search for the filenames, too. i.e. If I search *.cpp, have to "grep cpp" otherwise I get nothing. So, the command you want is: find . -name \*.properties -print -exec grep listen {} \; (If you don't escape "*.properties", then find will fail if there's a file in the current directory).
flatcap · 226 weeks and 6 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands



Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: