git-annex-findcomputed(1)

git-annex-findcomputed 💖

okay bestie, this is a General Commands Manual page from the git-annex crew — it's the one that shows you all the files that can be computed instead of just stored. sit down, grab a boba, we're doing this 🧋✨

✨ NAME ✨

git-annex-findcomputed — lists computed files 👑

🌸 SYNOPSIS 🌸

git annex findcomputed [path ...]

🦋 DESCRIPTION 🦋

So like. This outputs a list of files in the path you gave it that can be computed by enabled compute special remotes. If you don't give it a path at all, it just lists files in the current directory and all its subdirectories. lowkey thorough of it 💅

Along with the name of each computed file, it shows you the input that was handed to git-annex-addcomputed(1). like, receipts. it's giving transparency ✨

For example:

# git-annex findcomputed foo.jpeg (imageconvert) -- convert file.raw
file.jpeg passes=10 bar.gz (compressor) -- compress bar --level=9

🎀 OPTIONS 🎀

• matching options — the git-annex-matching-options(1) can be used to specify which files get listed. no cap, filter away bestie 🔥
• --branch=ref — list computed files in the specified branch or treeish.
• --inputs — display each computed file followed by the input that is used to produce it. The current location of the input file in the work tree is displayed, but if the input file is not in the work tree, the key is displayed instead. (iconic fallback behaviour fr fr)

For example:

foo.jpeg file.raw bar.gz bar

When multiple input files are needed to compute a file, it outputs multiple lines for that file:

foo bar foo baz

• --format=value — use custom output formatting. 🎨

This option works the same as in git-annex-find(1), with these additional variables available for use in it: "${remote}", "${computation}"

The default output format is the same as --format='${file} (${remote}) -- ${computation}\n', except when outputting to a terminal, control characters will be escaped. (yes, escaped. don't freak out, it's for your own good 💀)

When --inputs is used, there are additional variables "${inputfile}" which is the input filename, "${inputkey}" which is the input key, and "${input}" which is either the filename or the key. The default output format for --inputs is the same as --format='${file} ${input}\n' To separate the pair of files by nulls instead, use eg --format='${file}\000${input}\n' — sneaky little \000 moment 🫶

• --json — Output the list of files in JSON format.

This is intended to be parsed by programs that use git-annex. Each line of output is a JSON object. programmer besties, this one's for you 💜

• --json-error-messages — Messages that would normally be output to standard error are included in the JSON instead. so instead of screaming into stderr, it tucks the screams into the JSON 🫠✨

🌈 SEE ALSO 🌈

• git-annex(1)
• git-annex-addcomputed(1)
• git-annex-recompute(1)
• git-annex-findcomputed(1)
• git-annex-find(1)

(yes it references itself. main character energy, we love that for it 👑)

💖 AUTHOR 💖

Joey Hess <id@joeyh.name>

that's the whole page bestie, every flag, every variable, every example — nothing skipped, nothing invented. vibe check passed ✅

okay and for the cute sign-off: this whole thing is git-annex-findcomputed(1), straight from the git-annex manual, authored by Joey Hess 💅 stay computed, stay caffeinated, and remember — the inputs are always in the work tree somewhere 🌸🦋✨