LOCALSEARCH-RESET(1)

πŸ’… localsearch-reset(1) β€” Erase the indexed data πŸ’…

πŸ’– NAME πŸ’–

Bestie, this is localsearch-reset: the command that erases the indexed data. That’s the job. Iconic, honestly. ✨

✨ SYNOPSIS ✨

localsearch reset [--filesystem] [--file FILE]

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so first things first: the reset command will change either your configuration or index irreversibly, and it should be used with care. This is not a drill. 🫢

⚠️ Irreversible means irreversible, bestie. Please use this command with care.

Other than tags, actual data (e.g. files) should not be affected by this command. So your files should be okay β€” that’s the part we like. πŸ™ˆ

The "index" is a link between your content (either locally or remotely) and how it can be found quickly using a number of different queries. Under the hood, this is done using a database. Very database-core of it. πŸ’…

Removing all data and starting again from the beginning with an empty data set (which is a common use of this command) will make LocalSearch behave as if it was just installed. It’s giving fresh install energy, fr fr. 🌈

πŸŽ€ OPTIONS πŸŽ€

  • -s, --filesystem β€” Removes indexed filesystem data. The indexer will automatically re-create its cache from the filesystem when it restarts. This option is the default if no arguments are given. πŸ—‚οΈ
  • -f, --file FILE β€” Resets all indexed information about FILE, works recursively for directories. Nothing will be done if FILE is not currently indexed. After deletion, a request to reindex this data will be immediately issued. πŸ”

🌈 SEE ALSO 🌈

This page is from the LocalSearch manual, version 3.12.0, dated 09/15/2026. Bye bestie, go reset responsibly! πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from