-
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
Even while a package is ignored, its items are kept in history #60
Comments
This is expected behavior. For some reason, you may want to re-enable item's parent package or just disable it on a given machine, but not on another one. This is in case KP is installed on a USB device for example (since it allows user/machine-specific configuration). Use |
I'm closing this as you seem not to have further question on it. |
I realized I only partly answered to this. In a future release, the Catalog will filter out items that are in the history and orphan. Which means such an item will remain stored in history but that it won't be visible in search results unless its parent package is loaded (i.e. existent and enabled). I'm reopening this issue until implementation. |
"Which means such an item will remain stored in history but that it won't be visible in search results unless its parent package is loaded" Lovely thing to hear! Decided recently to disable the bookmark package for a certain browser and being able to hide the leftover history items was something I wished was possible. |
Cool, this does seem to be the best solution. |
As stated in a previous comment, items that are in the history and orphans are now filtered out of the result list, as of v2.10. |
I've disabled a number of packages, but kept seeing their items - it was a while until I realized they were history items. Maybe the catalog doesn't keep track of the parents of history items, but it's a bit confusing to see results for sources you had disabled. Especially since you can only effectively remove them by clearing the history, which may be painful for a user with lots of usage and useful history.
The text was updated successfully, but these errors were encountered: