[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: result of completing-read contradicting require-match
From: |
Jean Louis |
Subject: |
Re: result of completing-read contradicting require-match |
Date: |
Sat, 2 Jul 2022 23:07:09 +0300 |
User-agent: |
Mutt/+ () (2022-05-21) |
* Yuri Khan <yuri.v.khan@gmail.com> [2022-07-02 22:56]:
> On Sun, 3 Jul 2022 at 02:29, Jean Louis <bugs@gnu.support> wrote:
>
> > REQUIRE-MATCH can take the following values:
> > - a function, which will be called with the input as the parameter.
> > If it returns a non-nil value, the minibuffer is exited with that value.
>
> > other way to persist asking until you get the true result is here:
> >
> > (defun rcd-repeat-until-not-empty-string (function &rest args)
> > "Repeat FUNCTION with optional ARGS until result is not empty string."
> > (let ((result))
> > (while (string-empty-p (setq result (apply function args))))
> > result))
>
> Based on the quoted part of the docstring, you could probably pass a
> function that returns t for an allowed value, and nil for disallowed
> values, including an empty string or nil.
Do you mean from `completing-read':
"- a function, which will be called with the input as the parameter.
If it returns a non-nil value, the minibuffer is exited with that value."
Do you mean this:
(let* ((cseq '("name" "name-mode"))
(csel (completing-read "Type: " cseq nil FUNCTION-HERE? nil )))
csel)
and what would be value name for function to check it?
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
Re: result of completing-read contradicting require-match, carlmarcos, 2022/07/02