unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: 60646@debbugs.gnu.org
Cc: luangruo@yahoo.com, err291@mail.usask.ca, drew.adams@oracle.com
Subject: bug#60646: 28.2; delete-selection-mode
Date: Sat, 14 Jan 2023 12:51:57 +0100	[thread overview]
Message-ID: <87sfgd8hb6.fsf@gmail.com> (raw)
In-Reply-To: <878ri5dihq.fsf@yahoo.com> (Po Lu via's message of "Sat, 14 Jan 2023 09:15:13 +0800")

Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:

> Drew Adams <drew.adams@oracle.com> writes:
>
>>> I would like to express my strong support
>>> for enabling delete-selection-mode by default.
>>> This is standard for almost all other text
>>> applications and feels unintuitive not to have it.
>>
>> +1.  I've advocated the same for decades.
>>
>> This should have happened when we turned on
>> `transient-mark-mode' by default.  And both
>> of those default-behavior changes should
>> really have happened long before that.
>
> I disagree, but we've had this argument before, so please just leave
> things as they are.
>
> Thanks.

Did we ever go through the length of making the sort of poll we had for
show-paren-mode?  I.e.

* deciding to poll users on emacs-devel,
  <E1mN4xu-0004y3-63@fencepost.gnu.org>

* announcing on info-gnu-emacs,
  <62f50784-593d-b302-b8b6-6d614ec37737@yandex.ru>

* collecting feedback on gnu-emacs-help,
  <9bc33df8-5c1b-cd82-f72e-6fc939990f37@yandex.ru>

* debriefing on emacs-devel.
  <2aed65dd-bcec-8e0e-e48b-7664a041f98b@yandex.ru>

Asking because

a) delete-selection-mode sounds (IMO) like one of these options that
meet the sweet (sour?) spot between triggering strong opinions ("Thou
Shalt Not Change Longſtanding Defaults", "But All Other Editors Do It",
"It Is Surprising And Destructive", "It Is Natural And Convenient"),
while being trivial to change in one's config either way,

b) For all the hassle it might have been, the poll and discussion around
it led to improvements to show-paren-mode, i.e. further fine-tuning of
the defaults.


I struggle to imagine how (b) could apply to delete-selection-mode, but
then again my imagination is very limited.  OTOH (a) might provide
enough justification for a poll, especially when coupled with the
recurring traffic that delete-selection-mode generates.

(Thinking of e.g. these emacs-devel megathreads:
 * <CAM-tV-8HZKJ9WKHXR0h8FC_Qv8YhjdAPYikcviD2HAUo6Msg4g@mail.gmail.com>
   (2018)
 * <20100318185435.GB1522@muc.de>
   (2010)

 Oh hey, well, (b) might not be off the table after all:

 > The _only_ problem I personally have with delete-selection-mode is
 > that it also replaces the region created by the likes of "C-x C-x",
 > something that "most software out there" does not and cannot do.  If
 > we were to change delete-selection-mode to replace only highlighted
 > text created by mouse selections or by shift-selections, I think we
 > could then enable it by default without much resistance, because
 > typing a character or DEL after explicitly selecting text is many
 > orders of magnitude less probable to be a mistake than when we make
 > the region active by other means.
 — <83o9d5q1bi.fsf@gnu.org>

 Enlightening; I personally C-x C-x C-g without a second thought when
 all I want is to "jump to mark" (or I use C-u C-SPC).  I use C-x C-x
 mostly for its region-activating effect (typically after C-y), rather
 than for its point-mark-swap effect, and I expect delete-selection-mode
 to clobber stuff I highlight with region-activating commands (C-M-SPC,
 C-x h, C-M-h, M-h, C-SPC + [move around]).

 But I understand how adding an option to control that would make sense)





  reply	other threads:[~2023-01-14 11:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-08  1:31 bug#60646: 28.2; delete-selection-mode Redekopp, Eric
2023-01-08 16:34 ` Drew Adams
2023-01-14  1:15   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-14 11:51     ` Kévin Le Gouguec [this message]
2023-01-14 12:34       ` Eli Zaretskii
2023-09-05 21:33         ` Stefan Kangas
2023-01-15  9:25       ` Visuwesh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sfgd8hb6.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=60646@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=err291@mail.usask.ca \
    --cc=luangruo@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).