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
Is your feature request related to a problem? Please describe.
Since #1692 got fixed, I want to move back to copyq from klipper (KDE's clipboard).
Describe the solution you'd like
So, is there a way to import from klipper directly? klipper saves its history as a .lst file, so maybe you can import from there? With a bit of work, you can also export klipper history is a plain text file, so maybe that could work as well (you would obviously lose date information, but order should still be preserved).
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
The history lst file seems to be some internal data format of Klipper. I'm not going to support this in CopyQ.
I took a quick peek at the implementation and to parse the file you would need to use Qt framework. Below is a simple script to import the data file with Python and PyQt5 library (it does not support import "url" and "image" type of objects, only simple text). Argument is path to the .lst file:
Is your feature request related to a problem? Please describe.
Since #1692 got fixed, I want to move back to copyq from klipper (KDE's clipboard).
Describe the solution you'd like
So, is there a way to import from klipper directly? klipper saves its history as a .lst file, so maybe you can import from there? With a bit of work, you can also export klipper history is a plain text file, so maybe that could work as well (you would obviously lose date information, but order should still be preserved).
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: