ffind: a sane replacement for command line file search

#1

Post by molbon » Sun, Jun 09, 2013, 12:38 PM UTC

ffind: a sane replacement for command line file search
wrongsideofmemphis.com

Re: ffind: a sane replacement for command line file search

#2

Post by revscat » Sun, Jun 09, 2013, 1:28 PM UTC

What are the advantages of this over

    mdfind -onlyin .

Re: ffind: a sane replacement for command line file search

#3

Post by msluyter » Sun, Jun 09, 2013, 1:37 PM UTC

Similarly, I have a little shell function loaded by .zshrc that covers 90% of my use cases:

   findit() {
       find . -name \* -exec grep -iH $1 {} \;
   }

Re: ffind: a sane replacement for command line file search

#4

Post by keeperofdakeys » Sun, Jun 09, 2013, 1:41 PM UTC

revscat wrote: post #2

What are the advantages of this over mdfind -onlyin .

The author probably wanted a simple command, that required as few parameters as needed.

Re: ffind: a sane replacement for command line file search

#5

Post by b0rsuk » Sun, Jun 09, 2013, 1:49 PM UTC

Alternatively, you may just install locate. It won't examine file contents, but it works in the common cases. It's also blazingly fast because it's indexed.

Re: ffind: a sane replacement for command line file search

#6

Post by taeric » Sun, Jun 09, 2013, 1:52 PM UTC

From reading this, I'm not entirely sure what makes this better than grep. I get why it is cool to have written it.

Re: ffind: a sane replacement for command line file search

#7

Post by resiros » Sun, Jun 09, 2013, 1:53 PM UTC

b0rsuk wrote: post #5

Alternatively, you may just install locate . It won't examine file contents, but it works in the common cases. It's also blazingly fast because it's indexed.

Its problem that you always have to update the index, which can be problematic in fast changing systems (and quite slow in some cases). The greatest disadvantage is that you need root rights to update the index.

Re: ffind: a sane replacement for command line file search

#8

Post by resiros » Sun, Jun 09, 2013, 1:54 PM UTC

I looked into his python implementation, I thought he would just translate the parameters and call find, but he instead did go to implement the search algorithm. Wouldn't that make it a bit slower than the original find?

Re: ffind: a sane replacement for command line file search

#9

Post by neurobashing » Sun, Jun 09, 2013, 2:15 PM UTC

This ffind isn't this ffind: https://github.com/sjl/friendly-find ?

Re: ffind: a sane replacement for command line file search

#10

Post by aarmot » Sun, Jun 09, 2013, 2:20 PM UTC

msluyter wrote: post #3

Similarly, I have a little shell function loaded by .zshrc that covers 90% of my use cases: findit() { find . -name \* -exec grep -iH $1 {} \; }

Author possibly meant something like this (but yeah, same idea) fffind () { find . -regex ".$1."; }