unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60527@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#60527: 30.0.50; Typing SPC in a minibuffer with completion
Date: Wed, 4 Jan 2023 19:45:45 +0200	[thread overview]
Message-ID: <0633641c-0fb3-8778-78b2-f9b827ca5b4a@yandex.ru> (raw)
In-Reply-To: <835ydmz0dh.fsf@gnu.org>

On 04/01/2023 19:16, Eli Zaretskii wrote:
>> Date: Wed, 4 Jan 2023 19:00:44 +0200
>> Cc:60527@debbugs.gnu.org,monnier@iro.umontreal.ca
>> From: Dmitry Gutov<dgutov@yandex.ru>
>>
>> On 04/01/2023 16:47, Eli Zaretskii wrote:
>>> I didn't say I'm against any change in this behavior.  Stefan proposed
>>> at least two alternatives that produce basically the same user-facing
>>> behavior when SPC is supposed to be interpreted verbatim, so they come
>>> very close to the alternative that you like better, but still stop
>>> short of breaking someone's muscle memory.
>> The first alternative provides sometimes the same, and sometimes
>> different behavior. In particular, when there are valid completions,
>> "SPC" would still perform completion -- something that I don't think
>> many users expect. Especially novices.
>>
>> The second alternative is even more involved, requiring
>> 'completing-read' callers to decide in advance whether the users will
>> want to have SPC insert SPC or perform completion. That's still odd and
>> seems like crossing the proper abstraction layers. The caller might not
>> know the collection contains spaces. And this approach can break
>> established muscle memory just the same, as soon as enough callers start
>> to make this choice.
> 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.

 > Many Emacs's abstractions leak from many
 > holes anyway.

That's more of a problem for a UI which is used in many, many places and 
in different contexts.





  reply	other threads:[~2023-01-04 17:45 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 [this message]
2023-01-04 18:37               ` Eli Zaretskii
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=0633641c-0fb3-8778-78b2-f9b827ca5b4a@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=60527@debbugs.gnu.org \
    --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).