Futilities/human/ff: Difference between revisions
< Futilities | human
Jump to navigation
Jump to search
(→Options: automatically-built table, yay) |
|||
| Line 30: | Line 30: | ||
==Examples== | ==Examples== | ||
Find all files in | * Find all files in my Downloads folder which were created or edited on August 26, 2022: | ||
./ff -fd:2022-08-26 -sp "/home/woozle/Downloads/*.*" | ./ff -fd:2022-08-26 -sp "/home/woozle/Downloads/*.*" | ||
Note that the quotes are necessary in order to prevent [[htyp:bash/globbing|bash from automatically unglobbing]] the "*.*" into a list of filenames. | : Note that the quotes are necessary in order to prevent [[htyp:bash/globbing|bash from automatically unglobbing]] the "*.*" into a list of filenames, which would hopelessly confuse things. | ||
* Look in my home folder and find all files with "signal" in the name, and log all folders searched: | |||
./ff -sp -lf:i=fo:f=folders.ff.log "/home/woozle/*signal*" | |||
: Note that this won't identify ''folders'' with "signal" in the name, which is actually what I wanted. This suggests that some tweaking may be needed, since <code>-lm:i=fo</code> should accomplish this but I don't think it does (not tested). Also, it's implied that matches and "found" can be written to separate logfiles, but I don't think it actually works that way. TO FIX. | |||
Revision as of 12:41, 22 October 2022
|
FF: File Finder
|
About
Yes, I know, there's find and grep but I find those both opaque and difficult to use.
Options
This list is in revision.
| name | |||
|---|---|---|---|
| standard | long | short | meaning |
| ff | --case-sensitive | -cs | case must match (I think this is just filenames for now, but might also be content...) |
| ff | --file-date= | -fd= | only include files created or edited on the given date |
| ff | --list-matches | -lm | log matching files (same suboptions as -lf) |
| ff | --show-commands | -sc | show any external commands used |
| spider | --list-found=<params> | -lf=<params> | list all items found according to the rules in <params>, which is formatted like "<name>=<value>:<name>=<value>":
|
| base | --config-file=<config spec> | -cf=<config spec> | name of config file to load instead of the default |
| base | --show-progress | -sp | update a line on the screen to show current activity |
old list
| options | ||
|---|---|---|
| long | short | meaning |
| --case-sensitive | -cs | case must match (I think this is just filenames for now, but might also be content...) |
| --file-date= | -fd= | only include files created or edited on the given date |
| --list-found | -lf | list all items as they are checked - fi for files, fo for folders, combine in either order for both |
| --log-matches | -lm | log found matches to a file |
| --show-commands | -sc | show any external commands used |
| --show-progress | -sp | display search progress on a single line (faster and less overwhelming) |
Examples
- Find all files in my Downloads folder which were created or edited on August 26, 2022:
./ff -fd:2022-08-26 -sp "/home/woozle/Downloads/*.*"
- Note that the quotes are necessary in order to prevent bash from automatically unglobbing the "*.*" into a list of filenames, which would hopelessly confuse things.
- Look in my home folder and find all files with "signal" in the name, and log all folders searched:
./ff -sp -lf:i=fo:f=folders.ff.log "/home/woozle/*signal*"
- Note that this won't identify folders with "signal" in the name, which is actually what I wanted. This suggests that some tweaking may be needed, since
-lm:i=foshould accomplish this but I don't think it does (not tested). Also, it's implied that matches and "found" can be written to separate logfiles, but I don't think it actually works that way. TO FIX.