From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 60527@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#60527: 30.0.50; Typing SPC in a minibuffer with completion
Date: Wed, 04 Jan 2023 20:37:30 +0200 [thread overview]
Message-ID: <83v8lmxi1h.fsf@gnu.org> (raw)
In-Reply-To: <0633641c-0fb3-8778-78b2-f9b827ca5b4a@yandex.ru> (message from Dmitry Gutov on Wed, 4 Jan 2023 19:45:45 +0200)
> Date: Wed, 4 Jan 2023 19:45:45 +0200
> Cc: 60527@debbugs.gnu.org, monnier@iro.umontreal.ca
> From: Dmitry Gutov <dgutov@yandex.ru>
>
> > I understand that just rebinding SPC is much easier. But we are
> > supposed to consider other factors, not just the ease of
> > implementation. And I'm not afraid of code that is somewhat inelegant
> > and even breaks abstractions, if we provide better, friendlier UI
> > which breaks less habits.
>
> Using proper abstractions is what can lead to predictable, better UI.
> And vice versa -- patching through special cases upon special cases
> leads to less predictable, worse UI.
>
> I wasn't talking about the ease of implementation, really.
Not necessarily.
And let's stop here and agree to disagree about this, okay?
next prev parent reply other threads:[~2023-01-04 18:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 19:05 bug#60527: 30.0.50; Typing SPC in a minibuffer with completion Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-03 20:14 ` Drew Adams
2023-01-04 18:17 ` Jean Louis
2023-01-03 22:50 ` Dmitry Gutov
2023-01-04 3:29 ` Eli Zaretskii
2023-01-04 12:05 ` Dmitry Gutov
2023-01-04 14:47 ` Eli Zaretskii
2023-01-04 17:00 ` Dmitry Gutov
2023-01-04 17:16 ` Eli Zaretskii
2023-01-04 17:45 ` Dmitry Gutov
2023-01-04 18:37 ` Eli Zaretskii [this message]
2023-01-04 7:09 ` Kévin Le Gouguec
2023-01-04 18:14 ` Jean Louis
2023-01-04 19:11 ` Jim Porter
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=83v8lmxi1h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60527@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--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).