emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: A weird warning and a test (eager macro expansion) error
Date: Tue, 05 Nov 2013 21:59:11 +0100	[thread overview]
Message-ID: <87zjpia7kw.fsf@bzg.ath.cx> (raw)
In-Reply-To: <8761s68wzn.fsf@Rainer.invalid> (Achim Gratz's message of "Tue, 05 Nov 2013 20:33:16 +0100")

Hi Achim,

Achim Gratz <Stromeko@nexgo.de> writes:

> This is caused by the following constructs in test-ob.el:
> (ert-deftest test-org-babel/inline-src_blk-default-results-replace-line-1 ()
>   (let ((test-line "src_sh{echo 1}"))
>     ;; src_ at bol line 1...
>     (org-test-with-temp-text
> 	test-line
> ert-deftest is a macro and when it gets expanded the let binding is not
> yet established, thus the expansion of test-line fails further down in
> the body.  I'm not sure if this is supposed to work or not.  The older
> Emacsen just didn't expand the macro at all so the body was interpreted
> at runtime, Stefan Monnier made this an error a while back in trunk,
> IIRC.  You might ask on emacs-devel for more details.

Thanks -- I remember we had this issue before.  I'm just surprise I'm
the first one to report it, I assume many people use a recent Emacs
with macro expansion done this way.

Can you ask this on emacs-devel and see what could be done?

Or someone else that grok the issue well?


  reply	other threads:[~2013-11-05 20:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05  7:31 A weird warning and a test (eager macro expansion) error Bastien
2013-11-05 19:33 ` Achim Gratz
2013-11-05 20:59   ` Bastien [this message]
2013-11-12 21:50     ` Achim Gratz
2013-11-13  8:58       ` Bastien
2013-11-13 18:19         ` Achim Gratz
2013-11-17 20:57           ` Achim Gratz

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:

  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=87zjpia7kw.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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