Brian J. Tarricone wrote:
>>>I'm on the ThunarClipboardManager class right now, and wondering what
>>>targets should be supported by Thunar.
>>>
>>>For example, Nautilus supports the x-special/gnome-copied-files and
>>>UTF8_STRING targets, while only the further can be used for both cut and
>>>c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benedikt Meurer wrote:
> I'm on the ThunarClipboardManager class right now, and wondering what
> targets should be supported by Thunar.
>
> For example, Nautilus supports the x-special/gnome-copied-files and
> UTF8_STRING targets, while only the fur
Jens Luedicke wrote:
>>>I'm on the ThunarClipboardManager class right now, and wondering what
>>>targets should be supported by Thunar.
>>>
>>>For example, Nautilus supports the x-special/gnome-copied-files and
>>>UTF8_STRING targets, while only the further can be used for both cut and
>>>copy.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benedikt Meurer wrote:
> I'm on the ThunarClipboardManager class right now, and wondering what
> targets should be supported by Thunar.
>
> For example, Nautilus supports the x-special/gnome-copied-files and
> UTF8_STRING targets, while only the fur
I'm on the ThunarClipboardManager class right now, and wondering what
targets should be supported by Thunar.
For example, Nautilus supports the x-special/gnome-copied-files and
UTF8_STRING targets, while only the further can be used for both cut and
copy. With UTF8_STRING, the clipboard content
