From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "T.F. Torrey" <tftorrey@tftorrey.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Macro expansion in new exporter
Date: Sat, 09 Feb 2013 09:04:16 +0100 [thread overview]
Message-ID: <87wquhewvz.fsf@gmail.com> (raw)
In-Reply-To: <87ehgqwgi3.fsf@lapcat.tftorrey.com> (T. F. Torrey's message of "Fri, 08 Feb 2013 16:08:36 -0700")
Hello,
tftorrey@tftorrey.com (T.F. Torrey) writes:
> Right now, though, it's giving me a small problem: in the export to
> HTML, macro's are not expanded, so I have {{{title}}}, for instance, in
> the HTML output.
>
> I haven't been following the list as closely as I'd like, so I'm hoping
> I missed something relevant in the changeover.
>
> If anyone has any ideas, I'd appreciate them before I go digging.
Macro expansion happens before export back-ends kick-in, as does Babel
code evaluation and file inclusion through #+include keywords. So the
problem (if there's one) doesn't come from ox-html.el.
On that topic, the main difference with the previous exporter is that
macros are now required to be in a context that can be parsed. Thus, for
example, the following is not a macro:
~{{{title}}}~
> Emacs : GNU Emacs 24.3.50.1 (i686-pc-linux-gnu, GTK+ Version 3.6.0)
> of 2012-12-24 on menkib, modified by Debian
> Package: Org-mode version 7.9.2+ (7.9.2+-GNU-Emacs-24-3 (commit 488eea) @ mixed installation! /usr/share/emacs/24.3.50/lisp/org/ and /home/tftorrey/.emacs.d/elisp/org/lisp/)
You have a mixed installation. You should perhaps fix this before trying
again.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-02-09 8:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 23:08 Macro expansion in new exporter T.F. Torrey
2013-02-09 8:04 ` Nicolas Goaziou [this message]
2013-02-12 10:00 ` T.F. Torrey
2013-02-12 17:56 ` Nicolas Goaziou
2013-02-12 20:30 ` T.F. Torrey
2013-02-13 16:36 ` Nicolas Goaziou
2013-02-15 10:21 ` T.F. Torrey
2013-02-15 13:05 ` Nicolas Goaziou
2013-02-15 20:42 ` T.F. Torrey
2013-02-15 21:17 ` Nicolas Goaziou
2013-02-15 22:37 ` T.F. Torrey
2013-02-15 21:26 ` Nick Dokos
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=87wquhewvz.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tftorrey@tftorrey.com \
/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).