From: Thomas S. Dye <tsd@tsdye.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Limit on macro snippet size?
Date: Mon, 14 Sep 2015 07:34:39 -1000 [thread overview]
Message-ID: <m2613cdhw0.fsf@tsdye.com> (raw)
In-Reply-To: <20150914170120.GF2932@chitra.no-ip.org>
Hi Suvayu,
Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> Hi Tom,
>
> On Mon, Sep 14, 2015 at 06:40:48AM -1000, Thomas S. Dye wrote:
>>
>> I couldn't find any information on this in the manual or the mailing
>> list, though I vaguely recall some discussion on the list a while back.
>>
>> Is there a limit on the length of text that a macro like this will
>> process?
>>
>> #+MACRO: green \textcolor{PaleGreen4}{$1}
>>
>> I have 2 and 3 line sections of text passed to $1 that worked last
>> spring, but fail now.
>
> Are you sure? Here is a 3 line macro that seems to work fine for me:
>
> non-uniform acceptance ratio. {{{note(Add note on RICH detectors
> relying on exactly this feature to discriminate between particle
> species.,inline)}}}
>
> I have attached a screenshot of the relevant part of the output pdf to
> 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 ...
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2015-09-14 17:34 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 [this message]
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
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=m2613cdhw0.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@gmail.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).