| > file system to hold data My bespoke clipboard manager also uses the filesystem as the primary data structure. h/$serial_number/$mime_type/{data, index} H for history. data has the actual paste data. index has metadata useful for search - window name, day name, I also include wifi network so I can find clipboard history in terms of place, if I remember it that way. It also includes a copy of the data file if it's a text paste. You can include anything really it's fairly flexible. You can write whatever executable you want to the *-posthook file and they are all executed with argv having the path to the history entry directory. You can then modify the index as you please. I have a few frontends to actually use this clipboard history as well. One is a gtk3 frontend searchbar + list below. Another is a cli fzf based thing. Since the data structure is just the filesystem it's really composable and amazing. Various things like blacklisting windows, "pausing" clipboard history, etc are all just files as well. If you create a pause file it will pause (there's an if test -f pause check). You can add a grep -E pattern to the blacklist file and it won't paste from those window names. Unlimited history since I don't care about space. But it does support wrapping around after N items. Sync with phones is one thing i have to figure out...syncing across my different computers is dead easy of course. |