Bug 162749

Version:           Klipper: v0.9.7 Qt: 3.3.8b (using KDE 3.5.8)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Important tasks would become possible, if klipper would provide
a dcop method or a kill signal to trigger saving of its history.
Currently it seems, there is only an interactiv possibility:
raise klipper menu, select "Quit" and restart klipper.

Example (1)
Problems like reported in http://bugs.kde.org/show_bug.cgi?id=152039
could easily be solved or mitigated:  imagine a simple crontab entry.
I wonder, wy #152039 did not deserve severity "important".

Example (2)
To save history AUTOMATICALLY on exit klipper currently depends on
KDE sessionmanager.  It seems to be impossible if one uses klipper with
another windowmanager, e.g. with openbox.
If we had a dcop method or a kill signal, we could easily drop a line
in a logout script.


Filed this issue to Debian bts too:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483229


Nevertheless:  for me klipper is the most beloved KDE application,
I am using it everyday for many years, cannot imagine to live without it,
set history size to 2048 and access EVERY text copied several weeks ago
within few seconds by a 3 to 6 character regular expression eases work
enormously :-))