all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: klm@nist.gov
Cc: emacs-devel@gnu.org
Subject: Requires better docstring: icomplete-completions function
Date: Fri, 23 Oct 2020 19:01:13 +0300	[thread overview]
Message-ID: <courier.000000005F92FE4B.000067F5@static.rcdrun.com> (raw)

This function is not well defined, I would like to use some built-in
Emacs completion that could replace packages that are not
built-in. But this function description does not tell me how
candidates structure looks like or what should be predicate.


icomplete-completions is a compiled Lisp function in ‘icomplete.el’.

(icomplete-completions NAME CANDIDATES PREDICATE REQUIRE-MATCH)

Identify prospective candidates for minibuffer completion.

The display is updated with each minibuffer keystroke during
minibuffer completion.

Prospective completion suffixes (if any) are displayed, bracketed by
one of (), [], or {} pairs.  The choice of brackets is as follows:

  (...) - a single prospect is identified and matching is enforced,
  [...] - a single prospect is identified but matching is optional, or
  {...} - multiple prospects, separated by commas, are indicated, and
          further input is required to distinguish a single one.

If there are multiple possibilities, ‘icomplete-separator’ separates them.

The displays for unambiguous matches have ‘ [Matched]’ appended
(whether complete or not), or ‘ [No matches]’, if no eligible
matches exist.





             reply	other threads:[~2020-10-23 16:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 16:01 Jean Louis [this message]
2020-10-23 18:07 ` Requires better docstring: icomplete-completions function Stefan Monnier
2020-10-24  6:21   ` Jean Louis

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=courier.000000005F92FE4B.000067F5@static.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=emacs-devel@gnu.org \
    --cc=klm@nist.gov \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.