From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: sfischme@uwaterloo.ca, emacs-orgmode@gnu.org
Subject: Re: Annotating org exporters
Date: Wed, 11 May 2016 08:01:06 -0700 [thread overview]
Message-ID: <87vb2kmyfh.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <874ma5qivl.fsf@uwaterloo.ca>
Hi Sebastian and all,
Sebastian Fischmeister <sfischme@uwaterloo.ca> writes:
> I'm still undecided between a regex replace and org-entities. Is there
> a straightforward way to define own directives for orgmode to then
> support something like the following?
>
> #+LaTeX_EXPORT: "=>":"$\rightarrow$"
>
> or more generic
>
> #+EXPORT_EXPAND: latex:"=>":"$\rightarrow$"
>
> Then I could just make these expansions part of the standard header in
> my org files.
Well, there are macros, which do something very similar. As far as I
know, they are the only way to achieve this kind of thing without some
Elisp.
You could do something like:
#+MACRO: => @@latex:$\rightarrow$@@
but that actually doesn't seem to work as is, I suspect because "=>" is
not an allowable macro name. (It works fine with an alphabetic name
like "ARR".) But even if you got it to work, you'd then have to type
Some text {{{=>}}} other text after the arrow
in your document, which sort of defeats the point of the nice, simple
"=>". If it were me, I'd opt for the regex replacement, and avoid
typing all the braces.
Best,
Richard
next prev parent reply other threads:[~2016-05-11 15:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 13:56 Annotating org exporters Sebastian Fischmeister
2016-05-10 15:04 ` Rainer M Krug
2016-05-10 15:19 ` Richard Lawrence
2016-05-11 5:31 ` Sebastian Fischmeister
2016-05-11 15:01 ` Richard Lawrence [this message]
2016-05-10 15:55 ` Rasmus
2016-05-10 18:10 ` Rainer M Krug
2016-05-10 22:29 ` Rasmus
2016-05-11 5:31 ` Sebastian Fischmeister
2016-05-11 9:49 ` Rasmus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb2kmyfh.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me \
--to=richard.lawrence@berkeley.edu \
--cc=emacs-orgmode@gnu.org \
--cc=sfischme@uwaterloo.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.