Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Even while a package is ignored, its items are kept in history #60
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.
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).
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.
changed the title from
Even while a package is ignored, its items are kept in history
Catalog: Even while a package is ignored, its items are kept in history
May 5, 2016
"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.