emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Selection changes in revno 100822


From: David De La Harpe Golden
Subject: Re: Selection changes in revno 100822
Date: Tue, 17 Aug 2010 22:07:34 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100620 Icedove/3.0.5

On 17/08/10 19:14, Eli Zaretskii wrote:
From: Miles Bader<address@hidden>
Date: Wed, 18 Aug 2010 01:50:50 +0900

Well of course there's currently an option to let you do it (I use it).

Doesn't that option also set PRIMARY upon selection?


Sometimes: If mouse-drag-copy-region is t _and_
x-select-enable-primary is t, then mouse-selection will set primary
as well as putting the selection on the kill-ring.

If mouse-drag-copy-region is nil and x-select-enable-primary is nil
and select-active-regions is t, then both mouse/keyboard selection will set primary, but _without_ putting it on kill ring.


I am confident a behaviour-only backward compatible set of less confusing customisations would be possible (i.e. you could achieve the same effects as older emacs, but with different customisations), I proposed one some years ago.

I am confident a fully backward compatible set of customisations that are apparently confusing as hell is possible. (i.e. you achieve the same effects as older emacs with the same customisations (including reverting any changed defaults)) - that's what we have.

I am not confident a fully backward compatible set of customisations that aren't confusing as hell is possible.








reply via email to

[Prev in Thread] Current Thread [Next in Thread]