At 11:13 AM 7/2/02 +0900, Stephen J. Turnbull wrote:
Under the conditions described above, it did. Setting the
interprogram cut/paste functions to nil results in the same behavior
as 20.4 AFAIK.
So I don't think this is true, and we should probably come to some sort of
consensus about what the various problems really are and put it in PROBLEMS.
From select-x.c:
/* If we already own the clipboard, don't own it again in the Motif
way. This might lose in some subtle way, since the timestamp won't
be current, but owning the selection on the Motif way does a
SHITLOAD of X protocol, and it makes killing text be incredibly
slow when using an X terminal. ARRRRGGGHHH!!!!
*/
[This is the pre-21.4 behavior which was fast but did not honor copy and
paste between Motif widgets and XEmacs. The comment is Jamie's AFAIK so
this behavior was the default for many years]
/* No, this is no good, because then Motif text fields don't bother
to look up the new value, and you can't Copy from a buffer, Paste
into a text field, then Copy something else from the buffer and
paste it into the text field -- it pastes the first thing again. */
[This is the default behavior for 21.4. The comment is Ben's and he made
the change in 21.4]
&& (!owned_p
/* Selectively re-enable this because for most users its
just too painful - especially over a remote link. */
|| x_selection_strict_motif_ownership)
[This option was added by me sometime in the 21.4 release cycle to allow
users to get back at the pre-21.4 behavior]
IMO we should consider making the default nil rather than t.
andy