unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Jean Louis <bugs@gnu.support>
Cc: 36745@debbugs.gnu.org
Subject: bug#36745: 27.0.50; completing-read with require-match nil does not accept spaces
Date: Sat, 20 Jul 2019 21:52:37 +0000 (UTC)	[thread overview]
Message-ID: <2a8dcbf8-aff7-44f4-ad81-c64fd53623dd@default> (raw)
In-Reply-To: <20190720210221.GF30653@protected.rcdrun.com>

> > FWIW: By default, both `?' and `SPC' are
> > self-inserting for completion in Icicles
> > (and have been since 2004).

(I should have said 2005.)

> > But this is configurable, with option
> > `icicle-completion-key-bindings'.
> 
> That is interesting. Thank you.
> 
> I have found that various completion libraries are
> re-using the completing-read when necessary, so I
> have to stick with completing-read for now, to
> keep it minimal, and later customizable.

(When global minor mode `icy-mode' is on, ordinary
`completing-read' automatically gives you Icicles
completion.  When the mode is off, it gives you
the vanilla Emacs behavior.)

But the point was not that you should use Icicles
to get this behavior.  The point was that vanilla
Emacs should offer it also.

I suggested this long ago.  After some time, at
least file-name completion was changed to let
`SPC' self-insert.

One can hope that at some point users will get
similar behavior, by default, for other completion
keymaps, not just for file names.

While waiting, you can bind `SPC' yourself to
`self-insert-command' or whatever else you want,
in any of the minibuffer keymaps.  For example,
bind it in `minibuffer-local-completion-map' and
`minibuffer-local-must-match-map'.
____


Some old mails about letting `SPC', `?', and `C-j'
self-insert by default during completion:

https://lists.gnu.org/archive/html/emacs-devel/2014-04/msg00246.html

https://lists.gnu.org/archive/html/emacs-devel/2014-11/msg01521.html

https://lists.gnu.org/archive/html/emacs-devel/2009-11/msg01045.html

https://lists.gnu.org/archive/html/emacs-devel/2007-06/msg01810.html

https://lists.gnu.org/archive/html/emacs-devel/2005-11/msg00245.html







  reply	other threads:[~2019-07-20 21:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-20 19:03 bug#36745: 27.0.50; completing-read with require-match nil does not accept spaces Jean Louis
2019-07-20 20:14 ` Drew Adams
2019-07-20 21:02   ` Jean Louis
2019-07-20 21:52     ` Drew Adams [this message]
2019-07-20 23:13       ` Jean Louis
2019-07-21  0:04         ` Drew Adams
2019-07-21  7:34           ` Jean Louis
2019-07-20 23:40 ` Michael Heerdegen
2019-07-21  7:27   ` Jean Louis
2019-07-21  9:55     ` Basil L. Contovounesios
2019-07-21 19:53     ` Michael Heerdegen
2019-07-21 23:24     ` Michael Heerdegen
2019-07-22  0:03       ` Drew Adams
2022-02-20 15:22       ` Lars Ingebrigtsen
2022-02-20 22:24         ` bug#36745: [External] : " Drew Adams
2019-07-21  9:54   ` Basil L. Contovounesios

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=2a8dcbf8-aff7-44f4-ad81-c64fd53623dd@default \
    --to=drew.adams@oracle.com \
    --cc=36745@debbugs.gnu.org \
    --cc=bugs@gnu.support \
    /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).