unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: carlmarcos--- via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,  carlmarcos@tutanota.com
Subject: Re: Placement of list within an interactive clause
Date: Thu, 14 Jul 2022 20:15:13 +0000	[thread overview]
Message-ID: <875yjz4fji.fsf@posteo.net> (raw)
In-Reply-To: <N6y9nJO--3-2@tutanota.com> (carlmarcos's message of "Thu, 14 Jul 2022 21:24:14 +0200 (CEST)")

carlmarcos--- via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:

> Jul 14, 2022, 18:34 by help-gnu-emacs@gnu.org:
>
>>> Does it make difference where the list statement is placed?
>>>
>>
>> Write the code the way you find most convenient.
>> The syntax is:
>>
>>  (defun FOO (...)
>>  (interactive EXP)
>>  ...)
>>
>> where EXP is *any* code whose evaluation returns a list of values.
>>
>> In that case an interactive call to FOO will behave like (apply #'FOO EXP)
>>
>>  Stefan
>>
>
> When using ` (interactive (list (if condition (body))))', would the
> commands in the body of the if statement form part of the list? Does
> the same apply if using ` (let ' instead of ` (if ', where the body be
> part of the list entries?

The interactive expression evaluates to a list that is applied to the
function.  So when you see

--8<---------------cut here---------------start------------->8---
(defun foo (...)
  (interactive (list arg1 arg2 ... argn))
  ...)
--8<---------------cut here---------------end--------------->8---

you can think imagine that an interactive call does

--8<---------------cut here---------------start------------->8---
(apply #'foo (list arg1 arg2 ... argn))
--8<---------------cut here---------------end--------------->8---



  reply	other threads:[~2022-07-14 20:15 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 18:14 Placement of list within an interactive clause carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-14 18:34 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-14 19:24   ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-14 20:15     ` Philip Kaludercic [this message]
2022-07-14 20:30     ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-14 20:52       ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-14 21:12         ` Stefan Monnier
2022-07-14 21:15           ` carlmarcos--- via Users list for the GNU Emacs text editor
     [not found]         ` <jwv7d4f761t.fsf-monnier+emacs@gnu.org-N6yYlrA----2>
2022-07-16 23:01           ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-17  2:38             ` Stefan Monnier
     [not found]             ` <jwvcze4pj2d.fsf-monnier+emacs@gnu.org-N790PCt----2>
2022-07-17  3:02               ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-17 13:34                 ` Stefan Monnier
2022-07-14 21:23       ` [External] : " Drew Adams
2022-07-14 22:31       ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-14 22:52         ` [External] : " Drew Adams
     [not found]         ` <SJ0PR10MB54881126A1B0DB238AE8B82BF3889@SJ0PR10MB5488.namprd10.prod.outlook.com-N6yu_1j----2>
2022-07-15 20:05           ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-15  7:26 ` Jean Louis
2022-07-15  8:19   ` Christopher Dimech
2022-07-15 10:14     ` Jean Louis
2022-07-15 10:32       ` Christopher Dimech
2022-07-15 21:03         ` Jean Louis
2022-07-15 21:22           ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-15 21:31             ` Jean Louis
2022-07-15 22:53               ` Christopher Dimech
     [not found]             ` <YtHcni0c1ZTL+V8R@protected.localdomain-N72lwEe----2>
2022-07-16 22:08               ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-16 23:40                 ` Jean Louis
2022-07-17  1:22                   ` [External] : " Drew Adams
2022-07-17  2:04                     ` RE: [External] : " Christopher Dimech
2022-07-17  1:53                   ` Christopher Dimech
2022-07-17  2:16                     ` Jean Louis
2022-07-17  2:46                       ` Christopher Dimech
2022-08-01 11:52       ` Emanuel Berg
2022-07-15 19:55   ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-15 21:08     ` Jean Louis
2022-07-15 21:54   ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-07-16 10:15     ` Jean Louis

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=875yjz4fji.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=carlmarcos@tutanota.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).