emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Doyley, Marvin M." <m.doyley@rochester.edu>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: New markup for revising manuscripts
Date: Fri, 10 Mar 2017 20:33:57 +0000	[thread overview]
Message-ID: <4F883241-1170-4E41-88AE-A13C99581597@ur.rochester.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 459 bytes --]

Hi there,

When revising manuscripts, I usually highlight the changes (response to reviewer) in red. I use typically do this as follows:
(1) #+latex_header: \newcommand{\response}[1]{\textcolor{red}{#1}}
(2) \response{changes)

Is there a more elegant way to do this ?  It would be nice if I could change the color of the select text in both org and the exported latex file to red. Seeing the highlighted text in org would be a huge plus.

Thanks
M

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]

             reply	other threads:[~2017-03-10 20:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 20:33 Doyley, Marvin M. [this message]
2017-03-10 20:56 ` New markup for revising manuscripts Eric Abrahamsen
2017-03-10 20:56 ` Kaushal Modi
2017-03-10 21:47   ` John Kitchin
2017-03-11 11:35     ` Doyley, Marvin M.
2017-03-11 12:49     ` Doyley, Marvin M.
2017-03-11 12:55       ` John Kitchin
2017-03-11 14:08         ` Doyley, Marvin M.
2017-03-11 18:22           ` John Kitchin
2017-03-11 23:26             ` Doyley, Marvin M.
2017-03-12 18:16               ` John Kitchin
     [not found]             ` <25102de79a684cbea8543fdd8cc40188@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-12 14:12               ` Eric S Fraga
     [not found]           ` <037b006014244b1d874f76eea80b0f3a@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-12 13:54             ` Eric S Fraga
2017-03-13 22:56     ` Doyley, Marvin M.
     [not found]     ` <6ac43f7bdf5a4070807af1dfee9be4ea@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-14  7:25       ` Eric S Fraga
     [not found] <63b8c6bce92349fe95acb0c37536e965@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-11 10:59 ` Eric S Fraga
  -- strict thread matches above, loose matches on Subject: below --
2017-03-11 13:41 John Kitchin
     [not found] <46e4a91c14b34c5682a51f7b9cd5f7bd@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-11 16:30 ` Eric S Fraga
2017-03-13 17:25 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=4F883241-1170-4E41-88AE-A13C99581597@ur.rochester.edu \
    --to=m.doyley@rochester.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).