From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Bug: New Exporter macro expansion
Date: Sat, 06 Oct 2012 10:53:29 +0200 [thread overview]
Message-ID: <80r4pcugl2.fsf@somewhere.org> (raw)
In-Reply-To: 87txu86lts.fsf@gmail.com
Hi Nicolas,
Nicolas Goaziou wrote:
> Hello,
>
> Jonathan Leech-Pepin <jonathan.leechpepin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
>> Hello all,
>>
>> I've found a few issues with the new exporter (tested using
>> org-e-latex and org-e-ascii) with regards to macro expansion on
>> export.
>>
>> Using the minimal org file below with Org-mode version 7.9.2
>> (release_7.9.2-402-ge5e49e @ d:/Apps/Emacs/site-lisp/org/) certain
>> macros do not expand as expected.
>>
>> #+begin_src org
>> ,#+TITLE: Test
>> ,#+author: testing
>> ,#+macro: sample export this text
>> ,#+macro: sample2 {{{sample}}} and this text
>> ,#+macro: table | hello | goodbye |
>> ,#+macro: table2 | hello | {{{sample}}} |
>>
>> ,* Sample headline
>>
>> {{{title}}}
>>
>> | Test | 1 |
>> | {{{TITLE}}} | {{{sample}}} |
>> {{{table}}}
>> {{{table2}}}
>> #+end_src
>>
>> {{{title}}}, as well as {{{author}}} do not expand at all when
>> exporting. In addition macros within table cells are treated as empty
>> text.
>
> This should be fixed now. Thank you for the report.
Did you go further in the thinking about what the macros will support in the
future? Such as: multiline macros, recursive macros, Babel blocks, etc.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-10-06 8:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 19:44 Bug: New Exporter macro expansion Jonathan Leech-Pepin
2012-10-06 8:34 ` Nicolas Goaziou
2012-10-06 8:53 ` Sebastien Vauban [this message]
2012-10-06 9:29 ` Nicolas Goaziou
2012-10-09 14:53 ` Jonathan Leech-Pepin
2012-10-10 11:59 ` Nicolas Goaziou
2012-10-10 19:10 ` Sebastien Vauban
2012-10-10 20:38 ` Nicolas Goaziou
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=80r4pcugl2.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).