GNU bug report logs - #76617
completing-read should accept spaces in require-match nil mode

Previous Next

Full log

Message #17 received at 76617 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: "rms <at> gnu.org" <rms <at> gnu.org>
Cc: "dancol <at> dancol.org" <dancol <at> dancol.org>,
 "76617 <at> debbugs.gnu.org" <76617 <at> debbugs.gnu.org>
Subject: RE: [External] : Re: bug#76617: completing-read should accept spaces
 in require-match nil mode
Date: Sun, 2 Mar 2025 19:39:11 +0000

> Perhaps SPC and ? should self-insert when they do not extend the
> completion text at all.  Would that behavior be convenient?

I don't think so, but mine's just one opinion.

I think that would lead to confusion, hurting
more than helping.

Plus, with some completion "frameworks" (I'd
call them just packages that enhance/extend
completion possibilities) you can switch the
kind of completion/matching on the fly, with
the same pattern (input in the minibuffer).

And in that case SPC or ? could, after such
a switch, suddenly lead to completions, or
vice versa.

I really think that keys that have actions
such as what SPC and ? have had should not be
keys for printable (i.e., insertable) chars.
There's no more reason to have `?' not be
inserting than there is for `#' or `@' to not
be inserting.

Better to use unprintable keys for non-insert
actions.  In my code I use `M-SPC' in place
of `SPC' and `M-?' in place of `?', for those
actions.

In general, in editable buffers, users shouldn't
need to use `C-q' to insert printable chars.

Just one opinion.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.