emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: swflint@flintfam.org (Samuel W. Flint)
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Why does evaluating a piece of Elisp code seemingly not expand	a macro?
Date: Fri, 15 Jan 2016 16:10:45 -0500	[thread overview]
Message-ID: <87pox2mtuy.fsf@turing.flintfam.org> (raw)
In-Reply-To: <87a8o7duj6.fsf@mbork.pl> (Marcin Borkowski's message of "Fri, 15 Jan 2016 11:08:45 +0100")

[-- Attachment #1: Type: text/plain, Size: 796 bytes --]

>>>>> Marcin Borkowski writes:

MB> This piece of code: #+BEGIN_SRC elisp :results value verbatim
MB> :exports both (defmacro forty-two () (* 6 7))

That is not a macro.  That's a function.  The return value of a macro
(the result of the last expression in the implicit progn) needs to be a
(quasi-)quoted expression.

This macro simply evaluates to 42.  This should be a function.

If you want a macro, you could have:

#+BEGIN_SRC: emacs-lisp
  (defmacro forty-two ()
            '(* 6 7))
#+END_SRC

For what you want, you could have it be:

#+BEGIN_SRC: emacs-lisp
  (defmacro forty-two ()
            `,(* 6 7))
#+END_SRC


[...]

HTH,

Sam

-- 
Samuel W. Flint
4096R/266596F4
      (9477 D23E 389E 40C5 2F10  DE19 68E5 318E 2665 96F4)
(λs.s s) λs.s s

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  parent reply	other threads:[~2016-01-15 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 10:08 Why does evaluating a piece of Elisp code seemingly not expand a macro? Marcin Borkowski
2016-01-15 10:57 ` Oleh Krehel
2016-01-17 22:56   ` Marcin Borkowski
2016-01-18 13:54     ` Stefan Monnier
2016-01-18 20:03       ` Marcin Borkowski
2016-01-18 20:19         ` Stefan Monnier
2016-01-15 21:10 ` Samuel W. Flint [this message]
2016-01-15 22:06   ` Nick Dokos
2016-01-15 22:24   ` 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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pox2mtuy.fsf@turing.flintfam.org \
    --to=swflint@flintfam.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbork@mbork.pl \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).