From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Macro Expansion Inconsistency
Date: Tue, 16 Dec 2014 19:03:08 -0800 (PST) [thread overview]
Message-ID: <107c0d7b-85e5-480a-a0a4-ebe4662cfad7@googlegroups.com> (raw)
In-Reply-To: <mailman.16262.1418782759.1147.help-gnu-emacs@gnu.org>
On Wednesday, December 17, 2014 7:49:21 AM UTC+5:30, Alexander Shukaev wrote:
> How to overcome it? Do you have any further recommendations on this macro?
>
> P.S. It's my first somewhat serious macro in Emacs Lisp ever, so I'd love
> to learn more from pros until I do something dumb.
Macros are super powerful ... and super hard.
My recommendations?
1. [Just an imperative version of Joost suggestons]:
use macroexpand to debug them ie see (info "(elisp)expansion")
ie if form is a macro-call you can debug it with
first using (macroexpand form)
and if that looks sane then
(eval (macroexpand form))
However...
2. Lisp IS Eval... its evaling all the time so you rarely need to write 'eval'
Macros are double eval-layer So you doubly dont need eval
next prev parent reply other threads:[~2014-12-17 3:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.16228.1418763453.1147.help-gnu-emacs@gnu.org>
2014-12-16 21:10 ` Macro Expansion Inconsistency Joost Kremers
2014-12-16 21:25 ` Alexander Shukaev
2014-12-16 21:46 ` John Mastro
2014-12-16 22:58 ` Alexander Shukaev
2014-12-16 23:14 ` Alexander Shukaev
2014-12-17 2:19 ` Alexander Shukaev
2014-12-17 10:04 ` Nicolas Richard
2014-12-17 14:03 ` Alexander Shukaev
2014-12-17 14:20 ` Stefan Monnier
2014-12-17 14:34 ` Alexander Shukaev
2014-12-17 14:21 ` Nicolas Richard
2014-12-17 14:52 ` Alexander Shukaev
2014-12-17 14:58 ` Nicolas Richard
2014-12-17 15:14 ` Alexander Shukaev
[not found] ` <mailman.16290.1418825041.1147.help-gnu-emacs@gnu.org>
2014-12-17 15:53 ` Barry Margolin
2014-12-17 16:01 ` Alexander Shukaev
[not found] ` <mailman.16262.1418782759.1147.help-gnu-emacs@gnu.org>
2014-12-17 3:03 ` Rusi [this message]
2014-12-17 9:21 ` Nicolas Richard
2014-12-16 23:20 ` John Mastro
[not found] ` <CAKu-7WzgoHH=zM_jxeVGMwzAne88nAoCUsLKQv9zUYo_amsjNg@mail.gmail.com>
2014-12-17 3:34 ` John Mastro
2014-12-17 3:41 ` John Mastro
2014-12-16 23:30 ` Stefan Monnier
2014-12-16 20:57 Alexander Shukaev
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=107c0d7b-85e5-480a-a0a4-ebe4662cfad7@googlegroups.com \
--to=rustompmody@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).