I think this is probably the culprit. I suspect what's happening is that own-selection is adding a nil-typed entry, but get-selection is requesting a STRING-typed entry and can't find it. Kind regards, Alastair. src/ChangeLog: 2000-07-18 Alastair J. Houghton <ajhoughton(a)lineone.net&gt; * select.c (get_selection_internal, own_selection_internal): Make the type default to STRING, rather than placing a nil type into Vselection_alist. --- ../orig/xemacs-21.2/src/select.c Sun Jul 16 12:32:58 2000 +++ xemacs-21.2/src/select.c Tue Jul 18 10:24:31 2000 ＠＠ -155,6 +158,9 ＠＠ && !EQ (how_to_add, Qreplace_all) && !NILP (how_to_add)) error ("how-to-add must be nil, append, replace_all, " "replace_existing or t."); + + if (NILP (data_type)) + data_type = QSTRING; /* Examine the how-to-add argument */ if (EQ (how_to_add, Qreplace_all) || NILP (how_to_add)) ＠＠ -502,6 +508,9 ＠＠ if (NILP (device)) device = Fselected_device (Qnil); + if (NILP (target_type)) + target_type = QSTRING; + #if 0 /* #### MULTIPLE doesn't work yet and probably never will */ if (CONSP (target_type) && XCAR (target_type) == QMULTIPLE) -- ____________________________________________________________ Alastair Houghton ajhoughton(a)lineone.net

>>>>> "Ben" == Ben Wing <ben(a)666.com&gt; writes: Ben> Alastair, this fixes part of the bug, the not the whole bug. If Ben> you do kill within emacs and then yank, things work fine. you Ben> also fixed the other problem, with kill appending too much -- Ben> thanks. However, if you kill text [either using C-w or choosing Ben> the Cut option on the menu], you cannot paste the text into Ben> another XEmacs; you get "no selection available". A similar bug Ben> occurs with the primary-selection interface. When you select Ben> text in an X app, it automatically gets put on the PRIMARY Ben> selection, and typically you can paste it into another app using Ben> the middle mouse button. Now, you can select text in an xterm Ben> and paste it into xemacs using the middle button; but reversing Ben> the apps and this doesn't work. in both cases, xemacs is failing Ben> in either successfully taking ownership of the selection or Ben> responding to a selection request from another app. [almost Ben> certainly the latter, the former is fairly simple and you haven't Ben> modified that code.] With all 3 recent selection fixes of the past few hours applied, this works in my xemacs: - C-k C-y within one xemacs - mouse drag within one xemacs, mouse-2 paste into another - mouse drag within xterm, mouse-2 paste into xemacs But, I can confirm Ben's experience that - mouse drag within xemacs, paste into xterm fails.

>>>>> "Ben" == Ben Wing <ben(a)666.com&gt; writes: Ben> martin, please also test selecting text and cutting with C-w in Ben> one xemacs, and pasting with C-y in another. this uses Ben> 'CLIPBOARD instead of 'PRIMARY. Apparently not for me. If I C-w in a post-Alastair XEmacs and C-y in a pre-Alastair XEmacs, I get ===> Selection is not a string: PRIMARY If I C-w in a post-Alastair XEmacs and mouse 2 paste in a pre-Alastair XEmacs, the killed text is inserted (presumably from the PRIMARY selection). Going the other way: If I C-w in a pre-Alastair XEmacs, then both C-y and mouse 2 paste in a post-Alastair XEmacs inserts the killed text. When going between two post-Alastair XEmacsen: C-w in one, C-y in the other gives: ===> Kill ring is empty But maybe I've customized my XEmacs too much...