all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Olson <mwolson@gnu.org>
Cc: 14121@debbugs.gnu.org
Subject: bug#14121: Fwd: Eager macroexpansion failure in Emacs 24.3
Date: Wed, 03 Apr 2013 14:41:34 -0400	[thread overview]
Message-ID: <jwvwqsjea4s.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAN4ruPiCpmnXR5kABhwkKTC6K5fDa-1SGUWdT0SzCJQ4583cbg@mail.gmail.com> (Michael Olson's message of "Tue, 2 Apr 2013 09:18:43 +0100")

tags 14121 notabug
thanks

> emacs --no-init-file --load ~/test-case.el
[...]
> In *Messages* buffer:
[...]
> Eager macro-expansion failure: (error "(erc-response\\.contents parsed) is
> not a valid place expression")

Not a big surprise:

   emacs24 -Q --batch -f batch-byte-compile test-case.el 
   
   In end of data:
   test-case.el:14:1:Warning: the following functions are not known to be
       defined: erc-response.contents, setf, erc-replace-regexp-in-string
   Wrote /home/monnier/tmp/test-case.elc

Emacs-24.3 tries to expand macros more eagerly (i.e. more like the
byte-compiler), so files that fail to byte-compile properly are also
likely to fail that eager macro-expansion.

But do note that the above message is somewhat harmless: when eager
macro-expansion fails, Emacs falls back on macro-expanding lazily as it
has always done.  IOW other than emitting the above message your code
should still work fine.


        Stefan





  reply	other threads:[~2013-04-03 18:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01 10:40 Eager macroexpansion failure in Emacs 24.3 Michael Olson
2013-04-02  8:18 ` bug#14121: Fwd: " Michael Olson
2013-04-03 18:41   ` Stefan Monnier [this message]
2013-04-03 18:47     ` Eli Zaretskii
2013-04-03 23:41       ` Michael Olson
2013-04-04  0:51         ` Stefan Monnier
2013-04-04  3:22           ` Michael Olson
2013-04-04 12:33             ` Stefan Monnier

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

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

  git send-email \
    --in-reply-to=jwvwqsjea4s.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=14121@debbugs.gnu.org \
    --cc=mwolson@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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.