For instance you said:
“find /usr/share -name FreeSans* | grep Oblique”

that could have been less overhead in memory and easier written/read as follows:

find /usr/share -name FreeSans* -name Oblique

The find command treats 2 ‘-name’ flags as a logical “AND” which for our purpose acts like a filter (grep). To get find to match “either” case we have to separate the ‘-name’ flags by a ‘-o’ (OR) flag

Example:

$ ls -1
11
111
1122
1212
1221
2131
3131

# Find all files with a 2 in the name
$ find -name ‘*2*’
./1221
./1212
./2131
./1122

# filter only the names with 22 out of the original list
$ find -name ‘*2*’ -name ‘*22*’
./1221
./1122

Now I bet I know what you are thinking, that just did the last ‘-name’ flag and did not really use both as a filter.

Then consider this:

# Find any names with a 2 AND a 31 in the name
$ find -name ‘*2*’ -name ‘*31*’
./2131

# Now find any with a 22 AND a 31
$ find -name ‘*22*’ -name ‘*31*’

# oops… none match, but there is a 31 file right?
# There is (2131), but none that have a 22 AND 31.
# This proves the AND works.

# Obviously we would like to prove that AND
# as well as OR work…
$ find -name ‘*22*’ -o -name ‘*31*’
./1221
./2131
./1122
./3131

Viola! No need for the overhead of the external call to grep!

Also above you use a “| xargs ls -lh”… try the “-ls” flag to find, it has the same effect without the external call to xargs or ls (twice the overhead).

find -size +10000k | xargs vlc

to play all those videos on cache to find out which mattered. Thanks again. I was wanting to refresh my knowledge on find command once more and this article certainly is a direction ahead.