all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Olson <mwolson@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "mwolson@gnu.org" <mwolson@gnu.org>,
	"14121@debbugs.gnu.org" <14121@debbugs.gnu.org>
Subject: bug#14121: Fwd: Eager macroexpansion failure in Emacs 24.3
Date: Thu, 4 Apr 2013 00:41:28 +0100	[thread overview]
Message-ID: <CAN4ruPjhDJz-_wGF110Cjbn7Q9C+GYe7i8x6bC8AhrhfS3tKaA@mail.gmail.com> (raw)
In-Reply-To: <83d2ubh2nh.fsf@gnu.org>

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

If the message really is harmless (and no change to the code is
recommended, which seems to be the case), then it really ought to be
removed completely.

On Wednesday, April 3, 2013, Eli Zaretskii wrote:

> > From: Stefan Monnier <monnier@iro.umontreal.ca <javascript:;>>
> > Date: Wed, 03 Apr 2013 14:41:34 -0400
> > Cc: 14121@debbugs.gnu.org <javascript:;>
> >
> > 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.
>
> Perhaps the failure message should mention that.
>


-- 
Michael Olson  |  http://mwolson.org/

[-- Attachment #2: Type: text/html, Size: 1275 bytes --]

  reply	other threads:[~2013-04-03 23: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
2013-04-03 18:47     ` Eli Zaretskii
2013-04-03 23:41       ` Michael Olson [this message]
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=CAN4ruPjhDJz-_wGF110Cjbn7Q9C+GYe7i8x6bC8AhrhfS3tKaA@mail.gmail.com \
    --to=mwolson@gnu.org \
    --cc=14121@debbugs.gnu.org \
    --cc=eliz@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.