Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Optional Tracker3 search backend

Open
#3,765 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
c
Domain
desktop, search

Research direction

Start by reviewing Nemo’s existing search backend and the Tracker support build flags referenced in #3093 and #3247. Define how an opt-in Tracker3 backend would coexist with the current engine, remain off by default, and fall back silently when the daemon is unavailable; done means indexed searches work without changing the default behavior.

Written by the indexing model from the issue text.

Description

Hello Linux Mint team!

I have a feature request, would you be open to Tracker3 as an opt-in search backend in Nemo, alongside the current engine?

On my own setup search has become slow, my documents and media directories keep growing, and walking them live for every query takes long enough that I usually use a second search tool instead. Indexed search elsewhere (Spotlight, Nautilus with Tracker) returns hits as you type, I think this is nowadays the expected behavior.

I know #321 asked something similar back in 2013 and was closed in 2018, but that one wanted to replace the existing engine. I am asking the narrower question of whether Tracker3 could live next to it as an opt-in option - default off, silent fallback if the daemon is not running. The build flag for Tracker support seems to exist already (#3093, #3247), it just is not exposed at runtime.

Happy to hear from you!

Dominant language
C
Stars
1.6k
Forks
368
Avg merge
8d 7h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxmint/nemo

All issues in linuxmint/nemo

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.