From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Avoid escaping braces in LaTeX export?
Date: Fri, 07 Jun 2013 14:27:26 -0700 [thread overview]
Message-ID: <87r4gdehmp.fsf@berkeley.edu> (raw)
In-Reply-To: 20130607204548.6fabee8f@aga-netbook
Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
> Dnia 2013-06-07, o godz. 10:26:31
> Richard Lawrence <richard.lawrence@berkeley.edu> napisał(a):
>
>> Here's my use case. I often create new commands in LaTeX to abstract
>> over some common pattern so I can easily type it and change it later
>> if necessary. For example, when taking notes on readings, I have a
>> command that makes its argument into an `inline comment' (basically
>> an aside to myself) defined as follows:
>>
>> #+LATEX_HEADER: \newcommand{\ic}[1]{{\footnotesize [~#1~]}}
>>
> Quick and dirty workaround (untested):
>
> #+LATEX_HEADER: \def\ic!#1!{{\footnotesize [~#1~]}}
>
> Of course, you may do \def\ic(#1){...}, \def\ic~#1~{...} etc. The
> "delimiter" characters may not appear in the argument, though (nesting
> is not supported!).
>
> This is very un-LaTeX-y (it is much lower-level TeX syntax), but it is
> occasionaly useful (and heavily used by LaTeX itself, btw - this is
> used among others for delimiting optional arguments).
Hmm, that does work for this case, thanks!
Still, this won't work directly for cases where I have loaded a LaTeX
package that provides a command which uses curly braces. (I could
redefine such commands, as above, but that could get real ugly, real
fast...). It seems like this a general problem that the exporter should
have a way to handle.
--
Best,
Richard
next prev parent reply other threads:[~2013-06-07 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 17:26 Avoid escaping braces in LaTeX export? Richard Lawrence
2013-06-07 18:45 ` Marcin Borkowski
2013-06-07 21:27 ` Richard Lawrence [this message]
2013-06-08 14:35 ` Eric S Fraga
2013-06-08 17:45 ` Richard Lawrence
2013-06-09 7:37 ` 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=87r4gdehmp.fsf@berkeley.edu \
--to=richard.lawrence@berkeley.edu \
--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).