Gabriel Brown
a68e4f6dcd
Settings had a search index and the launcher had script commands, and neither knew about the other: finding a setting meant opening Settings first and searching there. One command per page is now generated from the same sources the in-app search reads -- the sidebar page list, the group routing, and the schema labels -- so a setting searchable inside Settings is searchable from the launcher without a second list to maintain. Generating it surfaced a gap in the in-app search as well. Six pages had no vocabulary at all, because their contents come from the system rather than our schema, so searching "volume" found nothing in Settings either. They now carry entries, which improves both surfaces. The product prefix is dropped from every hand-written command title. The generated ones are qualified "Settings: <page>" instead: a bare page label collides with the feature of the same name, and two commands sharing a title are indistinguishable in a launcher. Claude-Session: https://claude.ai/code/session_01BRvzt4H8XXLPVH5MyYdk9L
11 lines
542 B
Bash
Executable File
11 lines
542 B
Bash
Executable File
#!/usr/bin/env bash
|
|
# Generated by scripts/panama-settings-commands -- do not edit by hand.
|
|
# @vicinae.schemaVersion 1
|
|
# @vicinae.title Settings: Notifications & Focus
|
|
# @vicinae.mode silent
|
|
# @vicinae.icon ../../icons/hicolor/scalable/apps/panama-settings.svg
|
|
# @vicinae.description Open Notifications & Focus in Settings.
|
|
# @vicinae.keywords ["settings", "notification duration", "critical notification duration", "notification history", "visible banners"]
|
|
|
|
exec "$HOME/.config/quickshell/scripts/panama-action" settings-page notifications
|