From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: "Doyley, Marvin M." <mdoyley@ur.rochester.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: latex newcommand in org
Date: Fri, 20 May 2016 19:45:12 +0100 [thread overview]
Message-ID: <87k2iomuvb.fsf@ucl.ac.uk> (raw)
In-Reply-To: <4623b22355d94329a72b69bd254e036d@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Marvin M. Doyley's message of "Fri, 20 May 2016 18:10:47 +0000")
On Friday, 20 May 2016 at 18:10, Doyley, Marvin M. wrote:
> Hi there,
>
> In my group, we typically response to reviewers comments (in latex) by first defining the following command in the header
>
> \newcommand{\response}[1]{\textcolor{red}{#1}}
> then marking up the text as follows
>
> \response{red text}
>
> I try to do the same in org, i.e., putting
> #+latex_header:\newcommand{\response}[1]{\textcolor{red}{#1}}
> then \response{BLAH BLAH} in the text. The only snag is that on export I get \response\{BLAH BLAH\}
Easiest solution is @@latex:\response{blah blah}@@ but that will lose you
all the org formatting. Longer solution is to use environments, such as
#+begin_response
blah blah blah
#+end_response
and define a "response" LaTeX environment, along these lines:
#+latex_header: \makeatletter\newenvironment{response}{\textcolor{red}}{}\makeatother
(untested)
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.92.1, Org release_8.3.4-775-g3308a5
next parent reply other threads:[~2016-05-20 18:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4623b22355d94329a72b69bd254e036d@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-20 18:45 ` Eric S Fraga [this message]
2016-05-20 19:50 ` latex newcommand in org Marcin Borkowski
2016-05-20 20:37 ` Doyley, Marvin M.
2016-05-20 21:00 ` Leslie Watter
2016-05-20 23:45 ` Doyley, Marvin M.
[not found] ` <600dd6834d16428ba8a66f9bdd1b0f14@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-21 11:00 ` Eric S Fraga
2016-05-21 16:24 ` Marcin Borkowski
2016-05-20 18:10 Doyley, Marvin M.
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=87k2iomuvb.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=mdoyley@ur.rochester.edu \
/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).