From: Bastien <bzg@altern.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Build fail with emacs 24.3.1
Date: Tue, 19 Mar 2013 18:14:17 +0100 [thread overview]
Message-ID: <87sj3rrzim.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87ehfhg5ni.fsf@Rainer.invalid> (Achim Gratz's message of "Thu, 14 Mar 2013 20:09:21 +0100")
Hi Achim,
Achim Gratz <Stromeko@nexgo.de> writes:
> Aside from the issue of whether using macros here is needed or
> appropriate, I can't find anything wrong with the macros or their use so
> far. If that upholds, the test not working points to a rather
> substantial bug in either the test framework or Emacs 24.3.
It's not too late to explore this.
> I'm not sure if there's a way to circumvent eager macroexpansion to
> test how it gets involved. Some further testing seems to point to
> the let clause that produces the contents list: it never seems to be
> adding anything coming from the parent.
Yeah... I've dugg quite far in many directions here, but I'm
stuck. Anyway, `org-export-define-backend' and its friends are
now defuns, since there is no good reason for them to be macros.
Thanks,
--
Bastien
next prev parent reply other threads:[~2013-03-19 18:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 7:39 Build fail with emacs 24.3.1 Neuwirth Erich
2013-03-13 11:58 ` Bastien
2013-03-13 12:53 ` Andreas Röhler
2013-03-13 12:56 ` Bastien
2013-03-13 20:07 ` Achim Gratz
2013-03-14 2:30 ` Bastien
2013-03-14 8:26 ` Achim Gratz
2013-03-14 11:26 ` Bastien
2013-03-14 12:28 ` Bastien
2013-03-14 19:09 ` Achim Gratz
2013-03-19 17:14 ` Bastien [this message]
2013-03-20 19:03 ` `org-export-define-backend' and its friends are now defuns (was: Build fail with emacs 24.3.1) Florian Beck
2013-03-20 22:58 ` `org-export-define-backend' and its friends are now defuns Bastien
2013-05-19 14:36 ` Build fail with emacs 24.3.1 Achim Gratz
2013-05-20 10:13 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2013-03-13 12:29 Susan Cragin
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sj3rrzim.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).