[Top][All Lists]

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

Re: select-active-regions, Emacs not X

From: Andreas Röhler
Subject: Re: select-active-regions, Emacs not X
Date: Fri, 03 Sep 2010 10:45:07 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; de; rv: Gecko/20100711 Thunderbird/3.0.6

Am 03.09.2010 08:47, schrieb Miles Bader:
Andreas Röhler<address@hidden>  writes:
24 works now so far after setting `select-active-regions' other than
always' 23 works right out of the box, as these setting is nil.

All I'm saying is: Probably you will get more bug reports, is the
default-setting of `select-active-regions' remains `always'.
[It isn't `always' by default, it's `t'; but I guess that's what you mean.]

Why do you think that?  If it `select-active-regions' _isn't_ set to t,
then emacs will operate inconsistently, which will confuse some users
and potentially be a source of bug reports.

Well, the default delivered presently is "always"

cus-start.el, line 201

  (select-active-regions killing
                    (choice (const :tag "always" t)
(const :tag "only shift-selection or mouse-drag" only)
                        (const :tag "off" nil))

"only" would work,

so why not change it to?
23 comes with "nil" as default.

See a unnecessary change of behaviour so far.

Since either setting will probably generate some bug reports, but the
current setting is only a problem when the user is running dubious apps
like klipper, it seems safer to keep the current defaults.


reply via email to

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