From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: delete-selection-mode as default Date: Tue, 18 Sep 2018 21:30:28 +0300 Message-ID: <83d0tafykb.fsf@gnu.org> References: <<83k1nxvm5j.fsf@gnu.org>> <<87sh2ih0bp.fsf@fastmail.fm>> <<770f48a8-664a-40ae-8e03-19f6aad248b6@default>> <<20180910181615.GA4829@ACM>> <> <<874lev3bq4.fsf@toy.adminart.net>> <<20180912131602.GA5582@ACM>> <<87d0tihxzw.fsf@toy.adminart.net>> <<20180913174640.GB4019@ACM>> <<8736udkuit.fsf@toy.adminart.net>> <<20180914104833.GA4103@ACM>> <> <<83k1nojgia.fsf@gnu.org>> <<874leq799e.fsf@toy.adminart.net>> <<835zz5ie17.fsf@gnu.org>> <<87musg0wyf.fsf@toy.adminart.net>> <<83va73f0mv.fsf@gnu.org>> <> <<83musegaf2.fsf@gnu.org>> <> <<3f242636-6fa4-4e36-a37b-86f1d7088aae@default>> <<83h8img39b.fsf@gnu.org>> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1537295434 16362 195.159.176.226 (18 Sep 2018 18:30:34 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 18 Sep 2018 18:30:34 +0000 (UTC) Cc: hw@adminart.net, spacibba@aol.com, joostkremers@fastmail.fm, npostavs@gmail.com, emacs-devel@gnu.org, yurivkhan@gmail.com, acm@muc.de, phillip.lord@russet.org.uk To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 18 20:30:29 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g2KlY-00048n-VB for ged-emacs-devel@m.gmane.org; Tue, 18 Sep 2018 20:30:29 +0200 Original-Received: from localhost ([::1]:42055 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g2Knf-0000HO-Cp for ged-emacs-devel@m.gmane.org; Tue, 18 Sep 2018 14:32:39 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51840) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g2Kmx-0000HJ-8b for emacs-devel@gnu.org; Tue, 18 Sep 2018 14:31:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g2Kmt-0006VX-Fi for emacs-devel@gnu.org; Tue, 18 Sep 2018 14:31:54 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:51177) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g2Klc-0005X4-2s; Tue, 18 Sep 2018 14:30:34 -0400 Original-Received: from [176.228.60.248] (port=3417 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1g2Klb-0006zU-AK; Tue, 18 Sep 2018 14:30:31 -0400 In-reply-to: (message from Drew Adams on Tue, 18 Sep 2018 10:42:21 -0700 (PDT)) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:229951 Archived-At: > Date: Tue, 18 Sep 2018 10:42:21 -0700 (PDT) > From: Drew Adams > Cc: yurivkhan@gmail.com, hw@adminart.net, spacibba@aol.com, > joostkremers@fastmail.fm, npostavs@gmail.com, emacs-devel@gnu.org, > acm@muc.de, phillip.lord@russet.org.uk > > > > What's the real use case for such temporary enabling/disabling of d-s-m? > > > And how is it different from just, well, enabling/disabling d-s-m? > > > > People who are against turning on delete-selection-mode presented > > several such use cases. > > I don't think so. I think you just postulated it, without any example. > Did someone who is against using d-s-m actually say that s?he > wanted to use it temporarily (and without turning d-s-m on, > whatever that means)? > > But I could be wrong - it's a long thread. Feel free to point us to > some mention by someone of such a use case. Or if that's not > possible, please remind us of (describe) such a case. Look for messages from Alan and Richard. I cannot afford searching for them, life is too short. > > > In any case, how do you envision enabling/disabling d-s-m as something > > > different from turning d-s-m on/off? If you want some key(s) to > > > enable/disable it, how is that different from just binding a key > > > (or keys) to `delete-selection-mode'? > > > > Why don't you ask the same question about transient-mark-mode? > > Why do you think I should do that? Because in that case we have a few commands that temporarily turn on transient-mark-mode. We don't tell users to turn it on and off explicitly. I thought it might be a good idea to have a similar feature for delete-selection-mode. > What's a use case for doing that, and how do you see someone > doing it (other than by hitting a key bound to d-s-m, for example)? See above: asked and answered. > > My idea was to extend the feature of region activation, which > > would avoid the need for turning on and off the mode. > > Why don't you please clarify that idea? What is it that you intend > for users to do, to enable/disable d-s-m "temporarily"? Something similar to what we do for turning on transient-mark-mode temporarily. > Maybe I'm the only one who finds your proposal vague. I posted > my questions about it only after it seemed that Yuri had the same, > or similar questions. If you want me to understand - and I would > like to, please try to elaborate. I explained the idea in so many words several times already. If it's still not clear, I guess I will have to give up.