From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.bugs Subject: bug#22296: 25.1.50; Document changes to `delete-selection-mode' Date: Sun, 3 Jan 2016 10:00:46 -0800 (PST) Message-ID: <68435980-44a2-4d33-8f64-8fbbdedb4a4e@default> References: <<<660d1a46-fd5a-460f-8f26-50ba9a52cc60@default>>> <<<83mvsmadhv.fsf@gnu.org>>> <<940d59ef-c3d6-42df-ba0c-602cc154d431@default>> <<834meua953.fsf@gnu.org>> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1451844086 8603 80.91.229.3 (3 Jan 2016 18:01:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 3 Jan 2016 18:01:26 +0000 (UTC) Cc: 22296@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Jan 03 19:01:13 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aFmxr-00020b-EU for geb-bug-gnu-emacs@m.gmane.org; Sun, 03 Jan 2016 19:01:11 +0100 Original-Received: from localhost ([::1]:42444 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFmxn-0003FL-IK for geb-bug-gnu-emacs@m.gmane.org; Sun, 03 Jan 2016 13:01:07 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58610) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFmxk-0003EZ-7X for bug-gnu-emacs@gnu.org; Sun, 03 Jan 2016 13:01:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aFmxi-0002RM-Si for bug-gnu-emacs@gnu.org; Sun, 03 Jan 2016 13:01:04 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:48640) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFmxi-0002R8-PN for bug-gnu-emacs@gnu.org; Sun, 03 Jan 2016 13:01:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aFmxi-0001kN-Dp for bug-gnu-emacs@gnu.org; Sun, 03 Jan 2016 13:01:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Drew Adams Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 03 Jan 2016 18:01:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22296 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 22296-submit@debbugs.gnu.org id=B22296.14518440596700 (code B ref 22296); Sun, 03 Jan 2016 18:01:02 +0000 Original-Received: (at 22296) by debbugs.gnu.org; 3 Jan 2016 18:00:59 +0000 Original-Received: from localhost ([127.0.0.1]:36860 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aFmxf-0001jz-IU for submit@debbugs.gnu.org; Sun, 03 Jan 2016 13:00:59 -0500 Original-Received: from aserp1040.oracle.com ([141.146.126.69]:22013) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aFmxd-0001jl-15 for 22296@debbugs.gnu.org; Sun, 03 Jan 2016 13:00:57 -0500 Original-Received: from aserv0021.oracle.com (aserv0021.oracle.com [141.146.126.233]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id u03I0nS7002647 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 3 Jan 2016 18:00:51 GMT Original-Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserv0021.oracle.com (8.13.8/8.13.8) with ESMTP id u03I0m1D031109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 3 Jan 2016 18:00:48 GMT Original-Received: from abhmp0010.oracle.com (abhmp0010.oracle.com [141.146.116.16]) by userv0121.oracle.com (8.13.8/8.13.8) with ESMTP id u03I0lKe025725; Sun, 3 Jan 2016 18:00:48 GMT In-Reply-To: <<834meua953.fsf@gnu.org>> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6691.5000 (x86)] X-Source-IP: aserv0021.oracle.com [141.146.126.233] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:111157 Archived-At: > > > If you know about other changes (that are not bugfixes), please name > > > them. > > > > Frankly, I do not understand all of the changes I see in the code > > since 24.3. There are a boatload of them. `diff' the Emacs 25 > > version against the 24.3 version. >=20 > You don't get to complain about the v25 version until you see its NEWS > complete. We aren't there yet. Yes, of course. > But yes, I did look at all the changes in that file since 24.3 > release, and all I saw was the one mentioned, and a couple of > bugfixes. That is all. >=20 > > 1. It "can now be used without transient mark mode" is misleading. > > > > You could always turn off t-m-mode (after turning d-s-mode on) > > and still use d-s-mode. (But you might have been surprised to see > > stuff disappear because you didn't notice what was in the region.) > > > > The changes for this seem to be: (1) d-s-mode does not automatically > > turn on t-m-mode now, and (2) d-s-mode does NOT have any effect unless > > you turn on t-m-mode temporarily. IOW, d-s-mode works now only with > > temporary t-m-mode; it no longer works with a non-active region. > > (And yes, this is a good change.) >=20 > NEWS is not a manual, it only gives summary of the changes. Of course; agreed. It is for notifying users of behavior changes. > If you think the 2 manuals don't describe enough of the current > behavior, feel free to submit bug reports about specific deficiencies. I think I've done that here. If you don't want to consider it, fine. > > 2. d-s-mode now supports rectangular regions (?). >=20 > I don't know what you are talking about, please give an example that > didn't work earlier. (AFAIK, it always supported rectangles in > conjunction with CUA mode, but maybe I'm mistaken.) Dunno. I'm just looking at the code, which seems to have changed quite a bit in this regard. If you think nothing has changed wrt behavior, then feel free to ignore this heads-up. > > 3. Command `delete-selection-repeat-replace-region' was added. > > It seems to be bound, so far, only in CUA mode (to `M-v'). > > Not real clear to me what this is about/for. >=20 > Read the commentary to the changeset. It was a bugfix related to CUA > features that used to work previously. OK. > > 4. Apparently you can no longer specify `kill' as the d-s behavior: > > (put 'some-command 'delete-selection 'kill). Well, it's still > > supported for now, but `kill' has been removed from the file-header > > Commentary, and the code comments say that it is deprecated. > > > > Why is this? Where is this deprecation documented? Why > > shouldn't a user or a library still be able to override a > > `delete-selection' setting for a given command, to specify > > it as `kill'? Not clear to me what this is about. > > > > 5. There is an additional, undocumented (why?) possible value > > for `delete-selection', which you can apparently put on a > > command's symbol: `delete-selection-uses-region-p'. Please > > consider documenting this (e.g., not just mentioning it in NEWS). > > > > 6. The default delete-selection behavior for multiple commands > > has apparently changed. For example, `open-line' now has the > > default behavior and not the `kill' behavior. Likewise, unloading > > (`delsel-unload-function') deals with a different command list. >=20 > We never documented any of this, and I see no reason to do so now. Really? The fact that you (apparently) can no longer specify that a given command is handled by killing the region? The fact that there is a new possible value for the property (what is it for)? How is a user supposed to understand how to use d-s-mode if these things are not documented - either in a doc string or in a manual? And we no longer announce deprecations? Except in code comments? Anyway, I've reported the problems I see. Do with the information what you will.