emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Stefan Vollmar <vollmar@nf.mpg.de>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: my-mini-table(something)
Date: Thu, 18 Jun 2009 13:40:41 +0200	[thread overview]
Message-ID: <A860D2E5-1C36-4A9B-B8D0-238F13D416E8@nf.mpg.de> (raw)
In-Reply-To: <53831.25060.qm@web28311.mail.ukl.yahoo.com>

Dear Giovanni,

excellent, many thanks!


is exactly what I was looking for.

(1) The release notes of 6.27 say:
 > Macro processing for export has been enhanced: > > - You can use  
arguments in a macro, for example > #+macro hello Greet the $1: Hello $1
which is just what I had been hoping for! This important change has  
not yet made it into org.pdf of the 6.27a distribution. Obviously,  
this gives you maximum flexibility even for more complex documents and  
should get due emphasis in the documentation.
(2) The next logical step is to collect a number of useful macros in  
one include file. However, when I use
#+INCLUDE: "./include.org"
which contains the MACRO, the macro expansion does not work (if the  
same MACRO statements are part of the org-file where I use them, they  
work just fine), all other org content is included as expected. Is  
this is a bug?

Warm regards,

On 18.06.2009, at 12:14, Giovanni Ridolfi wrote:

> --- Gio 18/6/09, Stefan Vollmar <vollmar@nf.mpg.de> ha scritto:
>> For one project, I used several statements like this
>> (simplified):
>> #+HTML: <table><tr><td><img
>> src="./images/icon.png"/></td><td<code>something</code></td></tr></ 
>> table>
>> #+HTML: <table><tr><td><img
>> src="./images/icon.png"/></td><td<code>other</code></td></tr></table>
>> The result looks exactly the way we have planned it,
>> however, ideally one would want to write:
>> \my-mini-table(something)
>> \my-mini-table(other)
> + you can use  yasnippet
> http://code.google.com/p/yasnippet/
> http://doc.norang.ca/org-mode.html#sec-15.1
> + Or macros? manual, chapter 12.1 Markup rules
>    Macro replacement
>    -----------------
>    You can define text snippets with
>           #+MACRO: name   replacement text
>    which can be referenced anywhere in the document (even in code
>     examples) with `{{{name}}}'.
> #+MACRO: my-mt-sth  #+HTML: <table><tr><td><img> src="./images/ 
> icon.png"/></td><td<code>something</code></td></tr></table>
> cheers
> Giovanni

Dr. Stefan Vollmar, Dipl.-Phys.
Max-Planck-Institut für neurologische Forschung
Gleuelerstr. 50, 50931 Köln, Germany
Tel.: +49-221-4726-213  FAX +49-221-4726-298
Tel.: +49-221-478-5713  Mobile: 0160-93874279
Email: vollmar@nf.mpg.de   http://www.nf.mpg.de

  reply	other threads:[~2009-06-18 11:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 10:14 my-mini-table(something) Giovanni Ridolfi
2009-06-18 11:40 ` Stefan Vollmar [this message]
2009-06-18 14:00   ` my-mini-table(something) Sebastian Rose
  -- strict thread matches above, loose matches on Subject: below --
2009-06-18 13:11 my-mini-table(something) giovanni.ridolfi
2009-06-19  5:42 ` my-mini-table(something) Carsten Dominik
2009-06-18  9:56 my-mini-table(something) Stefan Vollmar
2009-06-18 12:25 ` my-mini-table(something) Matthew Lundin

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=A860D2E5-1C36-4A9B-B8D0-238F13D416E8@nf.mpg.de \
    --to=vollmar@nf.mpg.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).