unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 73544@debbugs.gnu.org, dmitry@gutov.dev, monnier@iro.umontreal.ca
Subject: bug#73544: smerge key bindings awkward
Date: Sun, 13 Oct 2024 12:57:01 -0400	[thread overview]
Message-ID: <122D1E12-D860-41AC-A1CF-18ECCA20AD60@dancol.org> (raw)
In-Reply-To: <86bjzot1z6.fsf@gnu.org>



On October 13, 2024 12:13:49 PM EDT, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Sun, 13 Oct 2024 12:01:33 -0400
>> From: Daniel Colascione <dancol@dancol.org>
>> CC: monnier@iro.umontreal.ca, dmitry@gutov.dev, 73544@debbugs.gnu.org
>> 
>> 
>> 
>> On October 13, 2024 7:06:11 AM EDT, Eli Zaretskii <eliz@gnu.org> wrote:
>> >> Date: Mon, 30 Sep 2024 07:50:50 -0700
>> >> From: Daniel Colascione <dancol@dancol.org>
>> >> CC: dmitry@gutov.dev, 73544@debbugs.gnu.org
>> >> 
>> >Actually, I see that the first part of this is already there: we have
>> >a defcustom smerge-auto-leave, whose default is t.  So does it mean we
>> >can consider this bug fixed?
>> 
>> The default is what produces the problem.
>
>Sure, but you can customize it according to your needs.  It's been the
>default for the last 24 years, so I think reversing it after such a
>long time would need a lot of complaints.

It's a defect in the user interface. Going NIMBY on the core is no way to make great software. We need to be able to add new key bindings, new features, and sand down high friction parts of the UI, even if they've been bumpy for a long time. 

After a certain point, customizing the program to work around all the terrible inherited defaults the maintainers refuse to change becomes tantamount to maintaining a fork. I guess that's why Doom exists.






  reply	other threads:[~2024-10-13 16:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-29  3:30 bug#73544: smerge key bindings awkward Daniel Colascione
2024-09-29  5:35 ` Eli Zaretskii
2024-09-30 12:39   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-29 23:27 ` Sean Whitton
2024-09-30  0:33 ` Dmitry Gutov
2024-09-30  4:41   ` Daniel Colascione
2024-09-30 11:31   ` Eli Zaretskii
2024-09-30 12:28     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]       ` <86msjp2tya.fsf@gnu.org>
2024-09-30 14:50         ` Daniel Colascione
2024-10-13 11:06           ` Eli Zaretskii
2024-10-13 16:01             ` Daniel Colascione
2024-10-13 16:13               ` Eli Zaretskii
2024-10-13 16:57                 ` Daniel Colascione [this message]
2024-10-13 18:58                   ` Eli Zaretskii
2024-10-17 17:37                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-17 18:44                     ` Daniel Colascione
2024-10-21 23:56                       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-22  5:12                         ` Eli Zaretskii
2024-10-22 14:19                           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=122D1E12-D860-41AC-A1CF-18ECCA20AD60@dancol.org \
    --to=dancol@dancol.org \
    --cc=73544@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).