From: Jean Louis <bugs@gnu.support>
To: Drew Adams <drew.adams@oracle.com>
Cc: 36745@debbugs.gnu.org
Subject: bug#36745: 27.0.50; completing-read with require-match nil does not accept spaces
Date: Sun, 21 Jul 2019 01:13:34 +0200 [thread overview]
Message-ID: <20190720231334.GA32596@protected.rcdrun.com> (raw)
In-Reply-To: <2a8dcbf8-aff7-44f4-ad81-c64fd53623dd@default>
* Drew Adams <drew.adams@oracle.com> [2019-07-20 23:53]:
> > > 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'.
So far I understand, icicle is some external
library?
I still think it is bug, either in documentation
because it is not "any input" allowed, or in the
function, as if any input would be allowed, then
spaces should be accepted.
My example is that I am giving a prefix to the
subject of email, so completing-read is offering
like: TASK, EXPENSES UPDATED, READ THIS
Subject becomes:
TASK: Do this
or EXPENSES UPDATED: 2019-07-19 for Gabriel
then if I wish to enter "NEWS FROM EUROPE" I
cannot, as space is not accepted as such.
So it makes no sense logically, to accept
"EXPENSES UPDATED" as one option to complete, but
not to limit me or the user to one word "any
input".
Thus any input shall be named "one word" with C-q
SPC option in the description of the function or
spaces shall be allowed, one of those.
next prev parent reply other threads:[~2019-07-20 23:13 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
2019-07-20 23:13 ` Jean Louis [this message]
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=20190720231334.GA32596@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=36745@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).