unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 60527@debbugs.gnu.org
Subject: bug#60527: 30.0.50; Typing SPC in a minibuffer with completion
Date: Wed, 4 Jan 2023 21:14:14 +0300	[thread overview]
Message-ID: <Y7XB9vNKDPyHkDPz@protected.localdomain> (raw)
In-Reply-To: <jwva62za176.fsf@iro.umontreal.ca>

* Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors <bug-gnu-emacs@gnu.org> [2023-01-03 22:07]:
> I wish the SPC binding to `minibuffer-complete-word` would go because it
> makes it hard to type SPC in the minibuffer whenever there's completion.
> 
> Typing a SPC in a "minibuffer with completion" can be needed when the
> things we want to complete contains a SPC character (e.g. file names,
> which is why we disable that SPC binding when completing file names),
> but also when using completion styles like `orderless` which make the
> use of a SPC character to specify how to select the
> completion candidates.
> 
> So my favorite option is indeed to simply remove this binding.
> Those few users who like it and use it (probably long-time users of
> Emacs) could easily get it back with:

Thanks. It will help in my packages as I have completion which I need
to be editable by user, such as header, footer specification and
inserting space require knowing how to use `C-q SPC', not a big deal,
but it will help in usability.

For completion I use TAB, instead of space. Space goes slow word by
word, but I did not find use for it yet.

--
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/





  parent reply	other threads:[~2023-01-04 18:14 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
2023-01-04  7:09 ` Kévin Le Gouguec
2023-01-04 18:14 ` Jean Louis [this message]
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=Y7XB9vNKDPyHkDPz@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=60527@debbugs.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).