* x-select-request-type
@ 2007-11-17 10:38 Eli Zaretskii
2007-11-17 15:10 ` x-select-request-type Jan Djärv
2007-11-18 11:22 ` x-select-request-type Kenichi Handa
0 siblings, 2 replies; 5+ messages in thread
From: Eli Zaretskii @ 2007-11-17 10:38 UTC (permalink / raw)
To: Kenichi Handa; +Cc: emacs-devel
The doc string of x-select-request-type says, among other things:
If the value is nil, try `COMPOUND_TEXT' and `UTF8_STRING', and
use the more appropriate result. If both fail, try `STRING', and
then `TEXT'.
But the code only falls back on `STRING', I don't see it trying
`TEXT'. Am I missing something, or do we need to fix the doc string?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: x-select-request-type
2007-11-17 10:38 x-select-request-type Eli Zaretskii
@ 2007-11-17 15:10 ` Jan Djärv
2007-11-18 11:22 ` x-select-request-type Kenichi Handa
1 sibling, 0 replies; 5+ messages in thread
From: Jan Djärv @ 2007-11-17 15:10 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: emacs-devel, Kenichi Handa
Eli Zaretskii skrev:
> The doc string of x-select-request-type says, among other things:
>
> If the value is nil, try `COMPOUND_TEXT' and `UTF8_STRING', and
> use the more appropriate result. If both fail, try `STRING', and
> then `TEXT'.
>
> But the code only falls back on `STRING', I don't see it trying
> `TEXT'. Am I missing something, or do we need to fix the doc string?
>
>
You are right. The doc string is wrong.
Jan D.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: x-select-request-type
2007-11-17 10:38 x-select-request-type Eli Zaretskii
2007-11-17 15:10 ` x-select-request-type Jan Djärv
@ 2007-11-18 11:22 ` Kenichi Handa
2007-11-18 12:36 ` x-select-request-type Jan Djärv
1 sibling, 1 reply; 5+ messages in thread
From: Kenichi Handa @ 2007-11-18 11:22 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: emacs-devel
In article <ufxz5cg24.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> The doc string of x-select-request-type says, among other things:
> If the value is nil, try `COMPOUND_TEXT' and `UTF8_STRING', and
> use the more appropriate result. If both fail, try `STRING', and
> then `TEXT'.
> But the code only falls back on `STRING', I don't see it trying
> `TEXT'. Am I missing something, or do we need to fix the doc string?
For emacs-unicode-2, I'm just now improving selection
handling, and the docstring of x-select-request-type will
become as this:
------------------------------------------------------------
*Data type request for X selection.
The value is one of the following data types, a list of them, or nil:
`COMPOUND_TEXT', `UTF8_STRING', `STRING', `TEXT'
If the value is one of the above symbols, try only the specified
type.
If the value is a list of them, try each of them in the specified
order until succeed.
The value nil is the same as the list:
(UTF8_STRING COMPOUND_TEXT STRING)
------------------------------------------------------------
---
Kenichi Handa
handa@ni.aist.go.jp
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: x-select-request-type
2007-11-18 11:22 ` x-select-request-type Kenichi Handa
@ 2007-11-18 12:36 ` Jan Djärv
2007-11-19 2:14 ` x-select-request-type Kenichi Handa
0 siblings, 1 reply; 5+ messages in thread
From: Jan Djärv @ 2007-11-18 12:36 UTC (permalink / raw)
To: Kenichi Handa; +Cc: Eli Zaretskii, emacs-devel
Kenichi Handa skrev:
> In article <ufxz5cg24.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
>
>> The doc string of x-select-request-type says, among other things:
>> If the value is nil, try `COMPOUND_TEXT' and `UTF8_STRING', and
>> use the more appropriate result. If both fail, try `STRING', and
>> then `TEXT'.
>
>> But the code only falls back on `STRING', I don't see it trying
>> `TEXT'. Am I missing something, or do we need to fix the doc string?
>
> For emacs-unicode-2, I'm just now improving selection
> handling, and the docstring of x-select-request-type will
> become as this:
>
> ------------------------------------------------------------
> *Data type request for X selection.
> The value is one of the following data types, a list of them, or nil:
> `COMPOUND_TEXT', `UTF8_STRING', `STRING', `TEXT'
>
Should we not try UTF8_STRING first?
Jan D.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: x-select-request-type
2007-11-18 12:36 ` x-select-request-type Jan Djärv
@ 2007-11-19 2:14 ` Kenichi Handa
0 siblings, 0 replies; 5+ messages in thread
From: Kenichi Handa @ 2007-11-19 2:14 UTC (permalink / raw)
To: Jan =?ISO-2022-JP-2?B?RGobJChEKyMbKEJydg==?=; +Cc: eliz, emacs-devel
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=ISO-2022-JP-2, Size: 416 bytes --]
In article <474031B6.1040704@swipnet.se>, Jan Dj^[$(D+#^[(Brv <jan.h.d@swipnet.se> writes:
> > *Data type request for X selection.
> > The value is one of the following data types, a list of them, or nil:
> > `COMPOUND_TEXT', `UTF8_STRING', `STRING', `TEXT'
> >
> Should we not try UTF8_STRING first?
Ah, yes. The latest emacs-unicode-2 code does that, and
documented so.
---
Kenichi Handa
handa@ni.aist.go.jp
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2007-11-19 2:14 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-17 10:38 x-select-request-type Eli Zaretskii
2007-11-17 15:10 ` x-select-request-type Jan Djärv
2007-11-18 11:22 ` x-select-request-type Kenichi Handa
2007-11-18 12:36 ` x-select-request-type Jan Djärv
2007-11-19 2:14 ` x-select-request-type Kenichi Handa
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).