LOCALSEARCH-INFO(1)

📦
version 3.12.0 · 15 versions
, in arch rolling

💅 localsearch-info(1) 💅

okay so bestie, this is a page from the LocalSearch manual and it's genuinely so useful, we're gonna get through it together, no cap ✨

🌸 NAME 🌸

localsearch-info — retrieve information available for files and resources. that's it, that's the vibe 🫶

⭐ SYNOPSIS ⭐

localsearch info [options...] <file1> [[file2] ...]

🦋 DESCRIPTION 🦋

so localsearch info literally just asks for all the known metadata available for the file you give it. like, all of it. it's giving main character energy for your filesystem 💅

you can pass multiple file arguments and it'll pull info about multiple files all at once. iconic, honestly.

and the file argument can be either a local path or a URI — and it also does not have to be an absolute path. so yeah, be chill about it, it's flexible 🌈

✨ OPTIONS ✨

  • -f, --full-namespaces — by default, all keys and values reported about any given file come back in shortened form. for example nie:title is shown instead of http://tracker.api.gnome.org/ontology/v3/nie#title. that makes things way easier to see generally and the output is less cluttered, iykyk. this option reverses that, so FULL namespaces are shown instead. bestie it's long but sometimes you need the whole thing 🎀
  • -c, --plain-text-content — if the resource being displayed has nie:PlainTextContent (i.e. information about the content of the resource, which could be the contents of a file on the disk), then this option displays that in the output. so like, the actual content content 🙈
  • -m, --mount=<FILE> — if a removable device mount path is specified, the information will be retrieved from the specific database for this mount point. if it is not specified, the data will be obtained from the main instance. choose your fighter 💀
  • -o, --output-format=<FORMAT> — choose which format to use to output results. the supported formats are turtle, trig and json-ld. slay, pick your aesthetic ⭐
  • -e, --eligible=<FILE> — checks whether a file is eligible for indexing. there might be a number of factors why it is not, e.g. being in a non-indexed folder, via configuration or filters. like sorry babe, not everything makes the cut 😭

🔥 SEE ALSO 🔥

and that's the whole page, no notes 💖 this was brought to you by 3.12.0, dated 09/15/2026 — periodt, go index something bestie 🧚‍♀️✨

📦 where this page comes from