From: Nicolas Kowalski <Nicolas.Kowalski@imag.fr>
Subject: Re: Error with topic
Date: Tue, 22 Jan 2002 19:17:28 +0100 [thread overview]
Message-ID: <vqon0z6s11j.fsf@anie.imag.fr> (raw)
In-Reply-To: <m3sn8ygsmx.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 22 Jan 2002 19:14:30 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Nicolas Kowalski <Nicolas.Kowalski@imag.fr> writes:
>
>> completing-read("Move to topic: " (("Perso" "perso.bzh" "perso.famille" "perso.misc" "perso.solene") ("VERIMAG" "verimag.achats" "verimag.log" "verimag.misc" "verimag.security" "verimag.www") ("Lists" "list.debian.french" "list.freebsd.french" "list.gnus.ding" "list.guilde" "list.rsync" "list.samba") ("Misc" "INBOX" "nndraft:drafts") ("Gnus")) nil t nil gnus-topic-history nil)
>
> Isn't that about the same number of parameters that the
> `completing-read' function takes?
>
> (completing-read PROMPT TABLE &optional PREDICATE REQUIRE-MATCH INITIAL-CONTENTS HISTORY DEFAULT)
>
> What's the description of your `completing-read'?
Seems like `DEFAULT' is not included...
Here it is :
`completing-read' is a compiled Lisp function
-- loaded from "/home/dres/xemacs21/xemacs21-21.1.10/lisp/minibuf.elc"
(completing-read PROMPT TABLE &optional PREDICATE REQUIRE-MATCH INITIAL-CONTENTS HISTORY)
Documentation:
Read a string in the minibuffer, with completion.
Args: PROMPT, TABLE, PREDICATE, REQUIRE-MATCH, INITIAL-CONTENTS, HISTORY.
PROMPT is a string to prompt with; normally it ends in a colon and a space.
TABLE is an alist whose elements' cars are strings, or an obarray.
PREDICATE limits completion to a subset of TABLE.
See `try-completion' for more details on completion, TABLE, and PREDICATE.
If REQUIRE-MATCH is non-nil, the user is not allowed to exit unless
the input is (or completes to) an element of TABLE or is null.
If it is also not t, Return does not exit if it does non-null completion.
If INITIAL-CONTENTS is non-nil, insert it in the minibuffer initially.
If it is (STRING . POSITION), the initial input
is STRING, but point is placed POSITION characters into the string.
HISTORY, if non-nil, specifies a history list
and optionally the initial position in the list.
It can be a symbol, which is the history list variable to use,
or it can be a cons cell (HISTVAR . HISTPOS).
In that case, HISTVAR is the history list variable to use,
and HISTPOS is the initial position (the position in the list
which INITIAL-CONTENTS corresponds to).
If HISTORY is `t', no history will be recorded.
Positions are counted starting from 1 at the beginning of the list.
Completion ignores case if the ambient value of
`completion-ignore-case' is non-nil.
next prev parent reply other threads:[~2002-01-22 18:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 15:21 Nicolas Kowalski
2002-01-22 16:35 ` Nicolas Kowalski
2002-01-22 16:49 ` Lars Magne Ingebrigtsen
2002-01-22 16:52 ` Lars Magne Ingebrigtsen
2002-01-22 17:07 ` Nicolas Kowalski
2002-01-22 17:19 ` Lars Magne Ingebrigtsen
2002-01-22 17:31 ` Nicolas Kowalski
2002-01-22 17:36 ` Lars Magne Ingebrigtsen
2002-01-22 17:40 ` Nicolas Kowalski
2002-01-22 18:14 ` Lars Magne Ingebrigtsen
2002-01-22 18:17 ` Nicolas Kowalski [this message]
2002-01-22 18:24 ` Lars Magne Ingebrigtsen
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=vqon0z6s11j.fsf@anie.imag.fr \
--to=nicolas.kowalski@imag.fr \
/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 NNTP newsgroup(s).