Re: users and selection changes

[Miles Bader <miles@gnu.org>]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> If the question is "why doesn't copying something in X make it end up in
> the kill ring any more?", and the answer is "set variable foo to make
> that happen again", then I'd like to know the answer.  Because I'd
> really like to get that behaviour back.

If by "copying something in X" you mean, "use `copy' menu in some app
(firefox, gnome, etc)", then it should put that stuff in the Emacs
kill-ring by default now.

If by "copying something in X" you mean, "select something in Xterm", then:

   (setq x-select-enable-primary t)

The _problem_ with setting x-select-enable-primary is that now all
_Emacs_ selections end up in the kill ring too, which is almost
certainly Not What You Want.

My idea to get around that problem (expressed on the gnu.emacs.help
newsgroup) is to add a feature that makes emacs put all selections
_except_ those originating from itself (the current Emacs process) on
the kill ring.

That, would basically make things similar to how they used to be

[I don't know if this behavior should associated with non-nil
x-select-enable-primary by default, or only upon some special value of
x-select-enable-primary, e.g. (setq x-select-enable-primary 'others).

It _is_ somewhat quirky (although very convenient) behavior, which
argues for "special setting", but on the other hand, the current
behavior of x-select-enable-primary is almost useless, so ...]

Thanks,

-Miles

-- 
Suburbia: where they tear out the trees and then name streets after them.