bug#6802: 24.0.50; Yanking non-ASCII text from other X application leads to unicode escapes

[Jan D.]

On 2010-08-10 04:29, Kenichi Handa wrote:
> In article<4C603A4F.20006@swipnet.se>, Jan Djärv<jan.h.d@swipnet.se>  writes:
> > Nowdays I think the
> > default should be UTF8_STRING, and if that fails, try TEXT and then STRING.
>
> Why not COMPOUND_TEXT instead of TEXT above?  Please see the
> docstring of x-select-request-type.

I forgot about that.  It is better to try that before TEXT.

> Anyway, the current selection-related codes mix an abstract
> layer (something like interprogram-cut/paste-function) and
> X-specific layer in a chaos manner.  It seems that overhaul
> and re-design is necessary.

It is a bit of a mess.  Separation of interprogram cut/paste and X 
selections would be nice.

        Jan D.