[GH-ISSUE #338] Feature Request - Replace oldest history entries with newly copied items #188

New issue

Open

opened 2026-03-03 01:10:48 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 01:10:48 +03:00

Owner

Originally created by @fmaiabatista on GitHub (Jan 24, 2019).
Original GitHub issue: https://github.com/Clipy/Clipy/issues/338

Use case: I want to have an always-fresh list of the last 10 copied items in my Clipy list such that new entries should replace the oldest entries.

Example: If I set the "Max clipboard history size" to, say, 10, when I copy the 11th item it should replace my oldest entry (1st), such that my current list should now be 11...2.

Problem: Currently I have set the "Max clipboard history size" to 10, but once it fills up, the new items (11th and on) don't go to the list. The workaround is (to notice it has happened and remember) to use the "Clear History" button (either by clicking or via shortcut) to restart my list, losing the previous items (1...10) just to get the new ones on the list (11...empty).

Originally created by @fmaiabatista on GitHub (Jan 24, 2019). Original GitHub issue: https://github.com/Clipy/Clipy/issues/338 **Use case**: I want to have an always-fresh list of the last 10 copied items in my Clipy list such that new entries should replace the oldest entries. **Example**: If I set the "Max clipboard history size" to, say, 10, when I copy the 11th item it should replace my oldest entry (1st), such that my current list should now be 11...2. **Problem**: Currently I have set the "Max clipboard history size" to 10, but once it fills up, the new items (11th and on) don't go to the list. The workaround is (to notice it has happened and remember) to use the "Clear History" button (either by clicking or via shortcut) to restart my list, losing the previous items (1...10) just to get the new ones on the list (11...empty).

kerem commented

2026-03-03 01:10:48 +03:00

Author

Owner

@fmaiabatista commented on GitHub (Jun 22, 2021):

Coming back to using this tool two years later, only to find an old issue by me that's still unaddressed ;(

@fmaiabatista commented on GitHub (Jun 22, 2021): Coming back to using this tool two years later, only to find an old issue by me that's still unaddressed ;(