From: Jean Louis <bugs@gnu.support>
To: Heime <heimeborgia@protonmail.com>
Cc: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Elisp command calling (describe-function) interactively
Date: Mon, 24 Oct 2022 16:24:11 +0300 [thread overview]
Message-ID: <Y1aR+07jDovXU2YX@protected.localdomain> (raw)
In-Reply-To: <1Ns-Id_L3-q4fgbBiohfvomuITn0hB5HDeWMof33S9XrqobXC3U1rc_TRLaGni2UYRKZ8HZGtYX378P-vZhKmAJ1tnh5jgUL0C1BAicaEps=@protonmail.com>
* Heime via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2022-10-24 09:38]:
> Started with using completing-read for inputting the function name, but does not
>
> look that the use of completing-read is appropriate, because completing-read only
>
> accepts completion from a predefined list.
(completing-read PROMPT COLLECTION &optional PREDICATE REQUIRE-MATCH
INITIAL-INPUT HIST DEF INHERIT-INPUT-METHOD)
Read a string in the minibuffer, with completion.
PROMPT is a string to prompt with; normally it ends in a colon and a space.
COLLECTION can be a list of strings, an alist, an obarray or a hash table.
COLLECTION can also be a function to do the completion itself.
Function need not be predefined, function may run with some
dynamically generated data.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-10-24 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 4:44 Elisp command calling (describe-function) interactively Heime via Users list for the GNU Emacs text editor
2022-10-23 17:02 ` Heime via Users list for the GNU Emacs text editor
2022-10-24 13:24 ` Jean Louis [this message]
2022-10-24 0:35 ` Emanuel Berg
-- strict thread matches above, loose matches on Subject: below --
2022-10-24 1:29 Drew Adams
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=Y1aR+07jDovXU2YX@protected.localdomain \
--to=bugs@gnu.support \
--cc=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).