Re: Merging the pgtk branch

[Yuuki Harano]

On Sun, 01 Aug 2021 12:57:15 -0400,
        Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>>>> @@ -165,9 +168,9 @@ gui--selection-value-internal
>>>>  Call `gui-get-selection' with an appropriate DATA-TYPE argument
>>>>  decided by `x-select-request-type'.  The return value is already
>>>>  decoded.  If `gui-get-selection' signals an error, return nil."
>>>> -  (let ((request-type (if (eq window-system 'x)
>>>> +  (let ((request-type (if (memq window-system '(x pgtk))
>>>>                            (or x-select-request-type
>>>> -                              '(UTF8_STRING COMPOUND_TEXT STRING))
>>>> +                              '(UTF8_STRING COMPOUND_TEXT STRING 
>>>> text/plain\;charset=utf-8))
>>>>                          'STRING))
>>> 
>>> Is it useful to have "text/plain\;charset=utf-8" here when
>>> window-system is 'x', not 'pgtk'?
>>
>> I think no.  But the combination is not harmful.
> 
> What is the intended difference between `UTF8_STRING`
> and `text/plain\;charset=utf-8`?

I think there is nothing.
Wayland applications may want to use mime types as
wider type support.

X applications support `UTF8_STRING`.
Wayland applications normally support both of `UTF8_STRING` and 
`text/plain;charset=utf-8`.
But XWayland seems to support only `text/plain;charset=utf-8`.

Applications on both side of copy/paste negotiate the data type,
and non-acceptable types are just ignored.
X applications don't know `text/plain;charset=utf-8`, and it
is ignored.

So I added it.

-- 
Yuuki Harano