unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Emanuel Berg <moasenwood@zoho.eu>,
	help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Insert one of the flags automatically with tab completion.
Date: Tue, 26 Oct 2021 10:38:27 +0800	[thread overview]
Message-ID: <CAGP6POKWGeqsXQmjiU-_Dv6AC4Cypqe2ZX_kh8bgrHX7LDVCUw@mail.gmail.com> (raw)
In-Reply-To: <871r4azcgt.fsf@zoho.eu>

On Sun, Oct 24, 2021 at 11:09 PM Emanuel Berg via Users list for the
GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
> Hongyi Zhao wrote:
>
> >> Note that interactive and non-interactive use are not
> >> identical in one aspect ...
> >
> > Interactive is interacting with user as a command.
> > Non-interactive is called from within lisp code.
>
> Yes, interactive is a command, M-x CMD RET, or a keybinding.
>
> Non-interactive is from Lisp ...
>
> (`call-interactively' is the exception that proves the rule,
> and it should only be used when ... there is a reason to :))
>
> But that's not what I refered to actually, if you study the
> code you see the "nil t" that you asked about in the
> other thread -
>
> (defun atomic-position (flag)
>   (interactive
>    (list
>     (completing-read
>      "flag: " '("alat" "angstrom" "bohr" "crystal" "crystal_sg") nil t) ))
>   (insert (format "Atomic position: %s\n" flag)) )
>
> - and if you take a look at the docstring of `completion-read'
> you see that these arguments are for the
>
>   &optional PREDICATE REQUIRE-MATCH
>
> so the first nil says PREDICATE should be nil, it is already
> nil by default

What exactly does nil mean here?

The document says the following:

PREDICATE limits completion to a subset of COLLECTION.


> but we want to say that REQUIRE-MATCH should be
> t, so we say that PREDICATE is nil just to get to
> REQUIRE-MATCH if you follow, then we say it is t.
>
> And this is the difference from non-interactive use, because
> there is no such thing in the non-interactive part of the
> function. You can send any "flag" argument from Lisp and it
> will be processed.
>
> (atomic-position "darn")

(atomic-position "darn") ;; Atomic position: darn

> But M-x atomic-position RET darn RET ... try it.

0 flag (match required): darn

> Read (or look at) the docstrings, especially the
> interface/prototype part, to all functions you use ...

The lisp documentation is very obscure, and I often cannot grasp them
the first time I read it.

HZ



  reply	other threads:[~2021-10-26  2:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-23  5:07 Insert one of the flags automatically with tab completion Hongyi Zhao
2021-10-23  6:10 ` Hongyi Zhao
2021-10-23 19:23   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-24 14:50     ` Hongyi Zhao
2021-10-24 15:09       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-26  2:38         ` Hongyi Zhao [this message]
2021-10-26  5:14           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-26  5:22             ` Hongyi Zhao
2021-10-24 14:53     ` Hongyi Zhao

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=CAGP6POKWGeqsXQmjiU-_Dv6AC4Cypqe2ZX_kh8bgrHX7LDVCUw@mail.gmail.com \
    --to=hongyi.zhao@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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).