From: Barry Margolin <barmar@alum.mit.edu>
Subject: Re: elisp macros problem
Date: Mon, 26 Jul 2004 00:49:26 -0400 [thread overview]
Message-ID: <barmar-D2BD3E.00492626072004@comcast.dca.giganews.com> (raw)
In-Reply-To: ce1sfo$3ol$1@mughi.cs.ubc.ca
In article <ce1sfo$3ol$1@mughi.cs.ubc.ca>,
Lowell Kirsh <lkirsh@cs.ubc.ca> wrote:
> Yes, I have been making sure to quote the list, but it doesn't seem to
> work at all. I've also tried to macroexpand the forms I'm evaluating but
> the minibuffer just shows a condensed version of the expansion with lots
> of '...' placeholders. Is there a simple way to macroexpand and pretty
> print a form without the '...'s ?
Use the *scratch* buffer for a better interface to the Emacs Lisp R-E-P
loop.
>
> Lowell
>
> Barry Margolin wrote:
> > In article <ce1n4n$2gt$1@mughi.cs.ubc.ca>,
> > Lowell Kirsh <lkirsh@cs.ubc.ca> wrote:
> >
> >
> >>Why does this not work:
> >>
> >>(defmacro my-add-hooks (hooks &rest body)
> >> `(dolist (hook ,hooks)
> >> (my-add-hook hook ,@body)))
> >>
> >>??
> >
> >
> > It looks like it should work to me. Make sure you quote the list of
> > hooks when calling it, e.g.
> >
> > (my-add-hooks '(emacs-lisp lisp) (local-set-key ...))
> >
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
next prev parent reply other threads:[~2004-07-26 4:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 18:39 elisp macros problem Lowell Kirsh
2004-07-24 19:00 ` David Kastrup
2004-07-24 22:08 ` Lowell Kirsh
2004-07-24 23:41 ` David Kastrup
2004-07-25 1:58 ` Lowell Kirsh
2004-07-25 10:59 ` Kalle Olavi Niemitalo
2004-07-24 19:15 ` Barry Margolin
2004-07-24 19:59 ` Pascal Bourguignon
2004-07-24 20:50 ` David Kastrup
2004-07-24 21:49 ` Lowell Kirsh
2004-07-26 1:35 ` Lowell Kirsh
2004-07-26 1:55 ` Rahul Jain
2004-07-26 2:53 ` Lowell Kirsh
2004-07-26 4:05 ` Pascal Bourguignon
2004-07-26 4:13 ` Lowell Kirsh
2004-07-26 2:54 ` Lowell Kirsh
2004-07-26 22:16 ` Kalle Olavi Niemitalo
2004-07-26 22:58 ` Kevin Rodgers
2004-07-26 2:03 ` Barry Margolin
2004-07-26 3:06 ` Lowell Kirsh
2004-07-26 4:49 ` Barry Margolin [this message]
2004-07-26 5:20 ` Pascal Bourguignon
2004-07-26 6:10 ` Oliver Scholz
2004-07-26 5:55 ` David Kastrup
2004-07-27 6:38 ` Lowell Kirsh
2004-07-27 6:54 ` Lowell Kirsh
2004-07-27 7:14 ` David Kastrup
2004-07-27 8:10 ` Lowell Kirsh
2004-07-27 12:05 ` Pascal Bourguignon
2004-07-28 5:03 ` Rob Warnock
2004-07-31 20:46 ` Lowell Kirsh
2004-08-03 18:44 ` Michael Slass
2004-07-27 23:22 ` Barry Fishman
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=barmar-D2BD3E.00492626072004@comcast.dca.giganews.com \
--to=barmar@alum.mit.edu \
/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).