You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Maccy writes history to ~/Library/Containers/org.p0deje.Maccy/Data/Library/Application Support/Maccy/Storage.sqlite stores history when "Clear history on quit" is checkmarked.
Coming from KDE's Klipper, I assumed Maccy would only store history in memory with this option. I didn't really think twice about it until I noticed the wording and decided to double check
Solution
A sub-option for "Clear history on quit" that doesn't write history to disk
The text was updated successfully, but these errors were encountered:
Thank you for the feedback! This is not something I had on my mind, can you please provide more details about why you'd want this added?
Even though it might be possible to implement this via Core Data, I'm not sure how practical this would be. There are already multiple issues related to memory bloat (#384, #726) and the desire to keep unlimited history (#310) so I wonder how this would complicate the implementation, supporting simultaneously both disk/memory storage backends.
Before Submitting Your Feature Request
Problem
Currently Maccy writes history to
~/Library/Containers/org.p0deje.Maccy/Data/Library/Application Support/Maccy/Storage.sqlite
stores history when "Clear history on quit" is checkmarked.Coming from KDE's Klipper, I assumed Maccy would only store history in memory with this option. I didn't really think twice about it until I noticed the wording and decided to double check
Solution
A sub-option for "Clear history on quit" that doesn't write history to disk
The text was updated successfully, but these errors were encountered: