emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Limit on macro snippet size?
Date: Mon, 14 Sep 2015 22:03:37 +0200	[thread overview]
Message-ID: <20150914200337.GA30959@chitra.no-ip.org> (raw)
In-Reply-To: <m24miwdefm.fsf@tsdye.com>

On Mon, Sep 14, 2015 at 08:49:17AM -1000, Thomas S. Dye wrote:
> Hi Suvayu,
> 
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> 
> > Hey Tom,
> >
> > On Mon, Sep 14, 2015 at 07:34:39AM -1000, Thomas S. Dye wrote:
> >> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> >>
> >> > show it actually works.  How does the failure happen, what do you see in
> >> > the exported file?
> >> 
> >> \textcolor{PaleGreen4}\{the only weapons they had were a
> >> few stones in some of the Canoes and these they threw overboard
> >> when they found they were not wanted\}.
> >> 
> >> Note the curly brackets are escaped.  Not sure why ...
> >
> > Easy-peasy!  Org recognises the first {..} as part of a latex command,
> > not the later.  You need snippets.  I always use them to make export
> > more robust.  Try this:
> >
> > #+macro: green @@l:\textcolor{PaleGreen4}{@@$1@@l:}@@
> 
> This doesn't work for me.  The latex output isn't marked up, but the
> text passed to $1 appears in the tex file.

Sorry, I have a shortcut for latex snippets to l.  Try replacing the l
with latex:

#+macro: green @@latex:\textcolor{PaleGreen4}{@@$1@@latex:}@@

-- 
Suvayu

Open source is the future. It sets us free.

  reply	other threads:[~2015-09-14 20:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 16:40 Limit on macro snippet size? Thomas S. Dye
2015-09-14 17:01 ` Suvayu Ali
2015-09-14 17:34   ` Thomas S. Dye
2015-09-14 17:40     ` Suvayu Ali
2015-09-14 17:42       ` Suvayu Ali
2015-09-14 18:49       ` Thomas S. Dye
2015-09-14 20:03         ` Suvayu Ali [this message]
2015-09-14 20:25           ` Thomas S. Dye
2015-09-14 17:16 ` Eric S Fraga
2015-09-14 17:24   ` Rasmus
2015-09-14 17:34     ` Suvayu Ali

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=20150914200337.GA30959@chitra.no-ip.org \
    --to=fatkasuvayu+linux@gmail.com \
    --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).