From: Maciej Katafiasz <mathrick@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Elisp Tutorial dumb question -- but I thought I better doublecheck ??
Date: Wed, 25 Apr 2007 08:20:55 +0000 (UTC) [thread overview]
Message-ID: <f0n317$9nj$2@sea.gmane.org> (raw)
In-Reply-To: 1177431781.3373.8.camel@CASE
Den Tue, 24 Apr 2007 12:23:01 -0400 skrev William Case:
> The differences seem trivial, but can I re-write the lambda algorithm in
> terms of the defun algorithm for myself such that:
Not sure what you mean, but defun is simply defined in terms of lambda.
(defun foo (arg) "doc" body)
is the same as
(fset 'foo (lambda (arg) "doc" body))
next prev parent reply other threads:[~2007-04-25 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 16:23 Elisp Tutorial dumb question -- but I thought I better doublecheck ?? William Case
2007-04-25 8:20 ` Maciej Katafiasz [this message]
[not found] <mailman.2465.1177432345.7795.help-gnu-emacs@gnu.org>
2007-04-25 4:59 ` Barry Margolin
2007-04-25 6:14 ` Tim X
2007-04-25 8:26 ` Maciej Katafiasz
[not found] ` <mailman.2497.1177490263.7795.help-gnu-emacs@gnu.org>
2007-04-25 11:43 ` Tim X
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='f0n317$9nj$2@sea.gmane.org' \
--to=mathrick@gmail.com \
--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).