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

Previous Next

Full log

Message #17 received at 6802 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Kenichi Handa <handa <at> m17n.org>
Cc: kaloian <at> gnu.org, 6802 <at> debbugs.gnu.org
Subject: Re: bug#6802: 24.0.50;
	Yanking non-ASCII text from other X application leads to
	unicode	escapes
Date: Mon, 09 Aug 2010 19:34:23 +0300

> From: Kenichi Handa <handa <at> m17n.org>
> Date: Mon, 09 Aug 2010 11:57:12 +0900
> Cc: 6802 <at> debbugs.gnu.org
> 
> I can reproduce this bug.  In Emacs 23 mouse-2 was bound to
> mouse-yank-at-click which calls (x-get-selection 'PRIMARY
> 'UTF8_STRING) with this calling sequence.
> 
> mouse-yank-at-click
>   ->yank->current-kill
>     ->x-cut-buffer-or-selection-value
>       ->x-get-buffer
> 
> But, now mouse-2 is bound to mouse-yank-primary which
> directly calls (x-get-selection 'PRIMARY).  As the second
> optional arg DATA-TYPE is omitted, x-get-selection uses
> 'STRING for that.

Why does x-get-selection default to 'STRING?  Is that sensible
behavior?

> -  (let ((primary (x-get-selection 'PRIMARY)))
> +  (let ((primary (x-get-selection 'PRIMARY 'TEXT)))

Would it make sense to have x-get-selection default to 'TEXT instead?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.