Tags: N-R-K/clipmenu
Tags
6.1.0 - clipdel: Support getting pattern from standard input - clipmenu: Add support for CM_LAUNCHER=fzf - clipctl: Add clipctl utility to temporarily disable or enable clipmenud collection - clipmenud: Add temporary suspension with USR1 and USR2, usually controlled by clipctl - clipmenu: Add $CM_OUTPUT_CLIP to print the selected clip to stdout - clipmenud: Avoid noise when $cache_file does not exist yet
6.0.0 This is a big one, and one of the most fundamental releases we've had in years -- please take a look at the changelog to make sure you're still configured as you desire :-) - clipnotify is *mandatory* now. The old sleep polling method has been untested and unmaintained for a while, and it doesn't make sense to keep it as a viable code path. That means maintainer of clipmenu package should make sure clipnotify is a hard dependency for clipmenu, not an optdepend, as of this release. - The default for CM_OWN_CLIPBOARD changed from 1 to 0. We've had innumerable bugs reported over the years because of this feature, and while there have been some workarounds, the feature is only useful in some niche circumstances anyway, and causes enough pain otherwise to be disabled by default. You can still enable it with CM_OWN_CLIPBOARD=1. - The internal format for storing clips changed a little, but enough to require a new major version. As such, a fresh cache directory will be used by default for CM_DIR, to avoid any conflicts. - clipmenud now has a sessionwide lock to avoid multiple daemons running unintentionally at once. Lacking this resulted in a couple of hard to reproduce bug reports. - We now always vacuum unreferenced clips in batches instead of deleting them up front. This is an implementation detail, but should help a lot in avoiding bugs like in the past where a still-referenced clip has been deleted due to missing context at the deletion site. - A utility, clipfsck, was added to check for inconsistencies. Files without a cache entry are expected, as vacuums happen in batches, so don't worry if it reports that some files are orphaned. This tool is mostly for maintainer debugging, it's not recommended to be packaged.
PreviousNext