DIRVISH-LOCATE(8)
π NAME π
dirvish-locate β ok so bestie, this is the little icon that finds your file versions hiding inside your dirvish images. That's the whole job. Slay. β¨
πΈ SYNOPSIS πΈ
dirvish-locate vault[:branch] pattern
π¦ DESCRIPTION π¦
So like. Locate versions of files in a dirvish vault. That's the vibe.
Here's the tea π: dirvish-locate goes through the index of every single image in the vault you named, hunting for paths that match your pattern. And when it finds one? It reports that path, and then it gives you the modification time of every version of that file, plus every image that has a link to it. Full receipts. No cap. π
You can also hit it with the optional branch thing β vault:branch β and it will restrict the search to just that branch. Keep it focused, queen. π
Images that have an error status get skipped, and so do any images that don't have index files at all (no index, no entry, sorry babe π). Oh and heads up β that index file can be compressed with gzip or bzip2. If you wanna know the deets on that, go look at tree and index in dirvish.conf(5).
Now about the pattern. It's a perl regular expression that matches the final component of the path. So if you want to match any substring of the whole path, you gotta append .* to the end of your pattern. And if you want to anchor it to the end of the path, append $. Go read perlre(1) for the full lore, bestie, it's a whole thing.
Two things that are not getting matched, periodt:
- Directories β excluded, because otherwise they'd match literally every file inside them anyway. Makes sense, main character energy but no.
- Symlinks β also excluded. Bye. π
Now the important warning: if your pattern matches <em>way</em> too many paths, dirvish-locate will only report the matched paths and not the versions. And as a little sanity check, if the number of matches is <em>really</em> excessive, it'll even limit how many images it searches. Ngl, excessive matches is basically the universe telling you your pattern isn't specific enough. So take that path list it gave you and use it to compose a more specific one. Character development. π±
π EXIT CODES π
Okay so this part exists so you can automate and integrate dirvish-locate with other tools, and it gives you rationalised exit codes. They're range based, which is the key detail here.
β οΈ The code for one specific error might change from one version to the next β but it will always stay inside its specified range. So do not test for specific exit codes, test for a range of values. Fr fr. And to the degree possible, higher value ranges mean more severe errors. The numbers go up, the badness goes up. π
0β success β¨200-219β an error was encountered in loading a configuration file. π220-254β an error was detected in the configuration. π255β incorrect usage. bestie. what did you type. π
π FILES π
/etc/dirvish/master.confβ alternate master configuration file./etc/dirvish.confβ master configuration file.bank/vault/image/summaryβ image creation summary.bank/vault/image/indexbank/vault/image/index.gzbank/vault/image/index.bz2β dirvish index file.
(those last three are all the same thing, just one is plain, one is gzipped, one is bzip2'd π«Ά)
π SEE ALSO π
π§ BUGS π§
Nothing listed here, bestie. The section is empty. Not a single bug to report. Iconic behaviour, honestly. π
And that's the whole page!! π This was dirvish-locate(8) from the <b>System Manager's Manual</b> β go forth and locate your versions, you absolute legend. π¦β¨
π¦ where this page comes from
- fedora 43: dirvish 1.2.1-34.fc43 Β· OSL-2.0
- fedora 44: dirvish 1.2.1-36.fc44 Β· OSL-2.0
- nixos 26.05: dirvish 1.2.1
- nixpkgs unstable: dirvish 1.2.1
- opensuse-leap 16.0: dirvish 1.2.1-bp160.1.9 Β· OSL-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms