From: "Jan D." <jan.h.d@swipnet.se>
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: Tue, 10 Aug 2010 08:15:08 +0200 [thread overview]
Message-ID: <4C60EE6C.9040009@swipnet.se> (raw)
In-Reply-To: <tl7k4nzqjxf.fsf@m17n.org>
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.
next prev parent reply other threads:[~2010-08-10 6:15 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 ` bug#6802: 24.0.50; Yanking non-ASCII text from other X application leads to unicode escapes Eli Zaretskii
2010-08-09 17:26 ` Jan Djärv
2010-08-10 2:29 ` Kenichi Handa
2010-08-10 6:15 ` Jan D. [this message]
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=4C60EE6C.9040009@swipnet.se \
--to=jan.h.d@swipnet.se \
--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.