all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: Heime <heimeborgia@protonmail.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
	 Heime via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Subject: Re: Using conditional in interactive
Date: Mon, 16 Sep 2024 12:23:05 +0700	[thread overview]
Message-ID: <CAP_d_8X7v_gpLN0oU2iTkTbnmr_9D7rAqLe_h1JjACStD7KOKA@mail.gmail.com> (raw)
In-Reply-To: <_xNUYtOpBXEf1wLflhP345KZrcoNEnJvtk0-zpRm25Riea3-M-kH9cSKm4UorkXc1uv_HcHE_vm6zeKx6i7lzYC4OQ-aj6w65Bsl2waczcw=@protonmail.com>

On Mon, 16 Sept 2024 at 05:23, Heime <heimeborgia@protonmail.com> wrote:

> From you have described it, the cond should occur before the interactive
> clause, ending up with two interactive clause.  The one executed would
> depend on which condition succeeds.


An (interactive) clause is not executed. It is metadata which is
consulted before the function starts. You cannot apply normal
executable form reasoning to it.

From the point of view of the interactive call mechanism, there are
three possibilities:

* There is no interactive clause, in which case the function is not
callable interactively
* The first argument of the interactive clause is a string literal, in
which case it is interpreted according to the string interactive spec
rules.
* The first argument is not a string, in which case it is evaluated
and the result passed to the command.

A (cond) form is not a string.



      reply	other threads:[~2024-09-16  5:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 21:36 Using conditional in interactive Heime
2024-09-15 19:30 ` Michael Heerdegen
2024-09-15 20:50   ` Heime
2024-09-15 22:22     ` Heime
2024-09-16  5:23       ` Yuri Khan [this message]

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=CAP_d_8X7v_gpLN0oU2iTkTbnmr_9D7rAqLe_h1JjACStD7KOKA@mail.gmail.com \
    --to=yuri.v.khan@gmail.com \
    --cc=heimeborgia@protonmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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.