Content search.

ff() { local IFS='|'; grep -rinE "$*" . ; }
Grep will read the contents of each file in PWD and will use the REs $1 $2 ... $n to match the contents. In case of match, grep will print the appropriate file, line number and the matching line. It's just easier to write ff word1 word2 word3 Instead of grep -rinE 'word1|word2|word3' .
Sample Output
$ ff bin exit
./clfu:26:  exit 0
./cipa:6:exit 0

By: RanyAlbeg
2011-06-10 10:25:10

What Others Think

good job for an alias
magma_camel · 554 weeks and 3 days ago
Aliases do not take arguments.
RanyAlbeg · 554 weeks and 3 days ago
> Aliases do not take arguments. They do but local: can only be used in a function.
karol · 554 weeks and 1 day ago
No. Again - Aliases do not take arguments. I'm sorry.
RanyAlbeg · 554 weeks and 1 day ago
[karol@black test]$ type foo foo is aliased to `echo -e "1a\n2b\n3c\n4d" | grep -E ""$@"' [karol@black test]$ foo "2|4" 2b 4d
karol · 554 weeks and 1 day ago
I do not buy your tricks, old lady. It's not using the "$@" there. that's expanding to nothing. any arguments you pass to an alias just get tacked on to the end alias foo='printf "%s\n" 1a 2b 3c 4d | grep -E' foo '2|4' 2b 4d
RanyAlbeg · 553 weeks and 6 days ago
> any arguments you pass to an alias just get tacked on to the end Of course ;P [karol@black ~]$ type bar bar is aliased to `echo one "$1" two "$2"' [karol@black ~]$ bar 1 2 one two 1 2
karol · 553 weeks and 5 days ago
What are you trying to show? the 1 needs to be between 'one' 'two' and not at the end of the line. Your example shows exactly what I demonstrated earlier. Anyway, when you are thinking 'Should I use an alias or a function?' just use a function. Aliases do not holds code, functions do.
RanyAlbeg · 553 weeks and 4 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? 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.


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: