This adds an optional config.ron file to the pop_shell plugin and allows users to configure what desktop window attributes they want searched (e.g. window title and/or window description).
For example, I prefer the window name not to be searched, because it's often a web page that has set the title of the window (e.g. in Chromium). Because window items in the launcher list always sort above desktop apps, these active window HTML pages can get in the way of fast/memory muscle launcher usage.
My config is as follows (~/.local/share/pop-launcher/plugins/pop_shell/config.ron):
(
search: (name: false, description: true),
)
With the above config, even if I'm on a google search page for xournal++, typing xou into pop-launcher will always load my desktop app, "Xournal++", even if a Chromium HTML page has set the title to "Xournal++ Search Results". (Typing "chro", however, would still switch to Chromium).
This adds an optional
config.ronfile to thepop_shellplugin and allows users to configure what desktop window attributes they want searched (e.g. window title and/or window description).For example, I prefer the window name not to be searched, because it's often a web page that has set the title of the window (e.g. in Chromium). Because window items in the launcher list always sort above desktop apps, these active window HTML pages can get in the way of fast/memory muscle launcher usage.
My config is as follows (
~/.local/share/pop-launcher/plugins/pop_shell/config.ron):With the above config, even if I'm on a google search page for
xournal++, typingxouinto pop-launcher will always load my desktop app, "Xournal++", even if a Chromium HTML page has set the title to "Xournal++ Search Results". (Typing "chro", however, would still switch to Chromium).The default remains as it was, effectively:
Fixes #152