Feat/indexing UI - #1639
Open
Mestane wants to merge 63 commits into
Open
Conversation
…nd description layout
Mestane
force-pushed
the
feat/indexing-ui
branch
from
June 28, 2026 16:32
45f393a to
e605405
Compare
Mestane
force-pushed
the
feat/indexing-ui
branch
from
June 28, 2026 17:28
e605405 to
00b25d1
Compare
Mestane
force-pushed
the
feat/indexing-ui
branch
from
June 29, 2026 21:05
719c915 to
55c6491
Compare
Fall back to the project's fzf over entry titles when the inverted index has no exact or prefix match, so typos still find settings. Index results lead; fzf only fills the gaps.
Mestane
force-pushed
the
feat/indexing-ui
branch
from
June 29, 2026 21:14
55c6491 to
0f141e2
Compare
Mestane
force-pushed
the
feat/indexing-ui
branch
2 times, most recently
from
July 7, 2026 19:21
204ce53 to
d3ff68c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds full-text search to the settings panel. Typing a query shows grouped result cards that deep-link to the matching setting, scrolling to it and flashing it.
The index is now generated at runtime inside the shell. On first launch, the page QML files are parsed via
Quickshell.shellDirand an inverted index is written to~/.cache/caelestia/settings-index.json. Subsequent launches load the cached index instead of rebuilding it.The cache is keyed by the current Git revision, so every plugin update automatically invalidates and rebuilds the index. Search uses the cached inverted index with prefix matching, relevance ranking, and highlighted matches, while
fzfis only used as a fallback for typos.The previous build-time Python/QRC embedding has been removed. The entire indexing pipeline now lives in JavaScript, making it simpler and more consistent with the Caelestia architecture.
There's a developer guide in the README (collapsible section) covering how to add or remove settings from the index.