From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: lambda an (interactive) function but not a command
Date: Tue, 19 Mar 2019 02:39:32 +0100 [thread overview]
Message-ID: <87d0mnr6az.fsf@web.de> (raw)
In-Reply-To: <8636njejn8.fsf@zoho.eu> (Emanuel Berg's message of "Tue, 19 Mar 2019 02:29:47 +0100")
Emanuel Berg <moasenwood@zoho.eu> writes:
> You mean like this
>
> (lambda (interactive) () (gnus-summary-mail-forward 4))
>
> ?
No,
(lambda () (interactive) (gnus-summary-mail-forward 4))
please. Syntax is analogue to that of `defun': argument list comes
first. See the docstring of `lambda' :-)
Michael.
next prev parent reply other threads:[~2019-03-19 1:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 0:27 lambda an (interactive) function but not a command Emanuel Berg
2019-03-19 1:17 ` Michael Heerdegen
2019-03-19 1:29 ` Emanuel Berg
2019-03-19 1:38 ` Amin Bandali
2019-03-19 1:39 ` Michael Heerdegen [this message]
2019-03-19 2:03 ` Emanuel Berg
2019-03-19 2:49 ` quoting lambdas (was: Re: lambda an (interactive) function but not a command) Emanuel Berg
2019-03-19 14:15 ` quoting lambdas Michael Heerdegen
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=87d0mnr6az.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.
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).