From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: kaloian@gnu.org, 6802@debbugs.gnu.org
Subject: 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 [thread overview]
Message-ID: <83wrrzvj74.fsf@gnu.org> (raw)
In-Reply-To: <tl71va8sdbr.fsf@m17n.org>
> From: Kenichi Handa <handa@m17n.org>
> Date: Mon, 09 Aug 2010 11:57:12 +0900
> Cc: 6802@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?
next prev parent reply other threads:[~2010-08-09 16:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 13:56 bug#6802: 24.0.50; Yanking non-ASCII text from other X application leads to unicode escapes Kaloian Doganov
2010-08-09 1:46 ` David De La Harpe Golden
2010-08-09 2:57 ` Kenichi Handa
2010-08-09 14:06 ` bug#6802: 24.0.50; Yanking non-ASCII text from other X application leads to unicodeescapes Drew Adams
2010-08-09 16:34 ` Eli Zaretskii [this message]
2010-08-09 17:26 ` bug#6802: 24.0.50; Yanking non-ASCII text from other X application leads to unicode escapes Jan Djärv
2010-08-10 2:29 ` Kenichi Handa
2010-08-10 6:15 ` Jan D.
2010-10-28 12:10 ` Štěpán Němec
2010-10-29 2:18 ` Kenichi Handa
2010-10-31 0:38 ` David De La Harpe Golden
2010-10-31 16:05 ` Jan Djärv
2010-11-05 11:58 ` Kenichi Handa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wrrzvj74.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=6802@debbugs.gnu.org \
--cc=handa@m17n.org \
--cc=kaloian@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.