Re: long-standing set-up errors on upgrade (elimination of x cut buffers)

["Jan Djärv" <jan.h.d@swipnet.se>]

Joe Brenner skrev 2010-09-15 03.10:
> I see in NEWS
>
>    "*** Support for X cut buffers has been removed."
>
> For some time, I've had this in my emacs init files:
>
>    (setq x-select-enable-clipboard t)

This is now the default in Emacs 24.

>    (setq interprogram-paste-function 'x-cut-buffer-or-selection-value)

AFAIK, this has been the default since forever, why are you setting it?

>
> Now, with a recent build of bzr emacs, I see that leading to this error
> message:
>
>    current-kill:
>      Symbol's function definition is void: x-cut-buffer-or-selection-value

Replace with x-selection-value, but there is no point in setting it to the 
same value it already has.

>
> I personally am not actually fussy about the details of how X the
> clipboard talks to the kill-ring and vice versa.  I need there to be a
> way to do it, but it almost doesn't matter which way it is (e.g. I prefer
> a yank to snag the current X selection, but if I need to do a Control C
> first before that will work, I can live with that).
>
> But what I do find really disturbing is when stuff I've had in my set-up
> for years suddenly causes problems because I did an upgrade.
>
> (Of late, the gnus emacs team seems to be having trouble with the idea
> of stable interfaces.)

It is fairly common to have in .emacs stuff like:

(if (>= emacs-major-version 20)
    ...

for version specific settings.

We are moving from 23 to 24, i.e. a major upgrade.  Thus interfaces are not 
guaranteed to be the same.  Furthermore, in the development branches, things 
are likely to break from time to time.  Don't use Emacs trunk unless you can 
live with that.

	Jan D.