From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: (interactive) call or form?
Date: Mon, 09 Apr 2018 16:39:17 +0200 [thread overview]
Message-ID: <87zi2c78bu.fsf@web.de> (raw)
In-Reply-To: <86a7udr6vq.fsf@zoho.com> (Emanuel Berg's message of "Sun, 08 Apr 2018 18:38:01 +0200")
Emanuel Berg <moasen@zoho.com> writes:
> > So you think people understand "special form"
> > but don't understand "form"?
>
> In a way, yes, because "special form" sounds like something you don't
> understand, while "form" sounds like something you would understand,
> only you don't (probably), so it is more confusing.
These words name different things anyway: the first one is about the
binding of the function cell of the symbol `interactive', the other
names the whole s-exp "(interactive ...)". AFAIU the OP wanted a
description of the latter.
Michael.
next prev parent reply other threads:[~2018-04-09 14:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 3:52 (interactive) call or form? Marcin Borkowski
2018-04-08 9:32 ` Michael Heerdegen
2018-04-08 13:56 ` Drew Adams
[not found] ` <mailman.11853.1523179956.27995.help-gnu-emacs@gnu.org>
2018-04-08 14:52 ` Emanuel Berg
2018-04-08 15:55 ` Michael Heerdegen
[not found] ` <mailman.11888.1523202939.27995.help-gnu-emacs@gnu.org>
2018-04-08 16:38 ` Emanuel Berg
2018-04-09 14:39 ` Michael Heerdegen [this message]
2018-04-09 19:48 ` Marcin Borkowski
[not found] ` <mailman.11931.1523284766.27995.help-gnu-emacs@gnu.org>
2018-04-09 18:46 ` Emanuel Berg
[not found] <mailman.11840.1523159602.27995.help-gnu-emacs@gnu.org>
2018-04-08 4:32 ` Emanuel Berg
2018-04-09 19:54 ` Marcin Borkowski
[not found] ` <mailman.11946.1523303724.27995.help-gnu-emacs@gnu.org>
2018-04-09 20:58 ` Emanuel Berg
2018-04-10 4:29 ` Marcin Borkowski
[not found] ` <mailman.11960.1523334628.27995.help-gnu-emacs@gnu.org>
2018-04-10 18:32 ` Emanuel Berg
2018-04-13 14:40 ` Marcin Borkowski
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=87zi2c78bu.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
/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.