Bug 97913

Summary:	Clipboard / Selection Behavior enhancement
Product:	[Unmaintained] klipper	Reporter:	Dean M <dejanm>
Component:	general	Assignee:	Esben Mose Hansen <kde>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	adaptee, nate, travneff
Priority:	NOR
Version First Reported In:	0.9.6
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Dean M 2005-01-26 03:40:45 UTC

Version:           0.9.6 (using KDE KDE 3.3.2)
Installed from:    Slackware Packages

I think it would be very useful to implement the following functionality in Klipper:
1. When running in "Separate clipboard and selection" mode, Klipper should keep two separate history lists, display both of them and allow user to copy items between them.
2. It would be good if Klipper would allow user to specify "Bookmarks" - items that would be kept in separate list and that could be put onto clipboard at any time

Comment 1 richlv 2006-04-25 14:37:38 UTC

i like your first suggestion, but you really should file a separate report for each of the suggestions - that way it would be easier to manage them.

Comment 2 Julian Fleischer 2007-05-01 13:39:30 UTC

In Addition to Bug #144913 it would be cool if you could access these separate history lists via different context menus, i.e. left click for "real" clipboard, middle click for selection-clipboard.

Comment 3 Esben Mose Hansen 2009-09-21 20:05:55 UTC

We have plenty of reports asking for the 2nd feature (static items). No need to file more reports.

Comment 4 Jekyll Wu 2011-12-31 06:56:08 UTC

I'm curious why the reporter want another history dedicated for selection. 

From my daily experience, I often change mind on what should be copied several times before finally copying it. That means for one item in the clipboard history, there could be multiple items in the selection history. And I mostly only care about and reuse what I have copied in the past. The selection history does not seem useful to me.

Comment 5 Nate Graham 2021-04-01 21:11:20 UTC


*** This bug has been marked as a duplicate of bug 355841 ***