-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to disable auto-scanning #156
Comments
Yes, this is planned already; as well as per-package manual cataloging. |
@polyvertex Any update on this? |
Somehow... Not what you initially requested but per-package manual cataloging has been implemented for the next release. |
That's great! The point was to have manual/controlled cataloging ^^ Keep up the good work! |
Per-package manual cataloging is now available in v2.22. |
@polyvertex I hoped that the inclusion of manual scanning meant that this could optionally replace auto scanning... The manual options made things better (no restart of KP needed) but it's still cumbersome with OP case:
Presuming that always-on scanning is not somehow vitally bound to KP core all it would take is to have a global or per-package If there is an invalid item being searched for/launched, it could either be marked unavailable, display an error (Wox displays a tacky notification) or just hidden... |
Well, I didn't intend to close the issue in the first place, since, as mentioned in an earlier comment, only part of the request was implemented :) The setting will probably be named
As a side note, be aware there are the |
awesome \o/ thanks, this will be really useful |
With Keypirinha now storing the catalog in a persistent way, is there a way to disable auto-scanning? For users who just keep a set of manually updated items, this would be a performance boon (however marginal), and a way to keep the catalog items available even if targets are currently unavailable (eg. on an external/network drive, unloaded file container etc.). Users could trigger a scan manually (right click/refresh catalog).
The text was updated successfully, but these errors were encountered: