Hi John and Eric, I decided to adopt your approaches, thanks for the suggestions. So I can use either the response: or ++ to highlight changes in our manuscripts.
Cheers,
M
#+BEGIN_SRC emacs-lisp
(org-link-set-parameters
"response"
:export (lambda (keyword desc format)
(cond
((eq 'latex format)
(format "\\textcolor{red}{%s}" keyword))))
:face '(:foreground "red"))
#+END_SRC
#+begin_src emacs-lisp
(setq org-emphasis-alist
(cons '("+" '(:foreground "red"))
(delete* "+" org-emphasis-alist :key 'car :test 'equal)))
(custom-set-variables
'(org-latex-text-markup-alist '((bold . "\\textbf{%s}")
(code . verb)
(italic . "\\emph{%s}")
(strike-through .
"\\textcolor{red}{%s}")
(underline . "\\uline{%s}")
(verbatim . protectedtexttt))))
#+end_src
> On Mar 10, 2017, at 4:47 PM, John Kitchin <jkitc...@andrew.cmu.edu> wrote:
>
> You can .... wait for it... make a colored link ;):
> http://kitchingroup.cheme.cmu.edu/blog/2016/11/04/New-link-features-in-org-9/#org1bc1061
>
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__kitchingroup.cheme.cmu.edu_blog_2016_11_04_New-2Dlink-2Dfeatures-2Din-2Dorg-2D9_-23org1bc1061&d=DwMFaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=s3_3riAscdqtNAzgOuwYB9g0dZVGcp8BNCy_RylYdxU&m=9mMx6WEAeP-9u7CL3pjKmlORa7XXy-8WSBSwibTQWuo&s=4DUIBEXq8WNk6qHHyXFoIwWG4FlD2NlDgz8AfT2VUS0&e=>
>
> The example there has an html export defined, but you could as easily define
> a latex exporter. It has some limitations, like it might not reliably work on
> multiple lines, and you would not want to "highlight" across elements (or the
> latex will get ugly and probably not work).
>
> I have been working on some ways to get persistent highlighting using
> overlays for a similar purpose:
> http://kitchingroup.cheme.cmu.edu/blog/2016/11/10/Persistent-highlighting-in-Emacs/
>
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__kitchingroup.cheme.cmu.edu_blog_2016_11_10_Persistent-2Dhighlighting-2Din-2DEmacs_&d=DwMFaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=s3_3riAscdqtNAzgOuwYB9g0dZVGcp8BNCy_RylYdxU&m=9mMx6WEAeP-9u7CL3pjKmlORa7XXy-8WSBSwibTQWuo&s=I0JDZ741rHEtzWzAF3lhW65rzNn4vdq4tiUyD10_7l0&e=>
>
> so far I only can get reliable output to html. Latex seems possible, again if
> you don't highlight across too many elements. It is a work in progress here:
> https://github.com/jkitchin/scimax/blob/master/ov-highlighter.el
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_jkitchin_scimax_blob_master_ov-2Dhighlighter.el&d=DwMFaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=s3_3riAscdqtNAzgOuwYB9g0dZVGcp8BNCy_RylYdxU&m=9mMx6WEAeP-9u7CL3pjKmlORa7XXy-8WSBSwibTQWuo&s=2LS5YZIgyAvGS3fmo8rEgaDS2Tbu3UL10uqdUgH-LXc&e=>
>
> Towards the bottom of
> https://github.com/jkitchin/scimax/blob/master/cm-mods.el
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_jkitchin_scimax_blob_master_cm-2Dmods.el&d=DwMFaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=s3_3riAscdqtNAzgOuwYB9g0dZVGcp8BNCy_RylYdxU&m=9mMx6WEAeP-9u7CL3pjKmlORa7XXy-8WSBSwibTQWuo&s=hg-nJ1pgNjsD6TM3dFMEX7IADrW9iwU8e3nvulj1lFc&e=>
> I was working on some ways to use the criticmarkup in conjunction with git
> diffs to automatically make these kinds of diffs.
>
> I can't say I am fully satisified by any of these solutions (that is why
> there are so many of them ;)
>
> John
>
> -----------------------------------
> Professor John Kitchin
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__kitchingroup.cheme.cmu.edu&d=DwMFaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=s3_3riAscdqtNAzgOuwYB9g0dZVGcp8BNCy_RylYdxU&m=9mMx6WEAeP-9u7CL3pjKmlORa7XXy-8WSBSwibTQWuo&s=9l9_vjFtxnWTTnFYN-Uy0mhhk-B5fKQeudqix5QWjqA&e=>
>
>
> On Fri, Mar 10, 2017 at 3:56 PM, Kaushal Modi <kaushal.m...@gmail.com
> <mailto:kaushal.m...@gmail.com>> wrote:
> I use this macro to highlight text in html/latex(pdf):
>
> #+MACRO: COLOR @@html:<span style="color:
> $1">$2</span>@@@@latex:\textcolor{$1}{$2}@@
>
> This is from https://github.com/fniessen/org-macros/blob/master/README.org
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_fniessen_org-2Dmacros_blob_master_README.org&d=DwMFaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=s3_3riAscdqtNAzgOuwYB9g0dZVGcp8BNCy_RylYdxU&m=9mMx6WEAeP-9u7CL3pjKmlORa7XXy-8WSBSwibTQWuo&s=XDOhI8-iVimfEcDs18oR3i-Yyuic8xnEQRrHQ7lRlqI&e=>
>
> Example use:
> {{{COLOR(red, This information is important.)}}}
>
> It doesn't though highlight the text in red in org-mode.
>
> On Fri, Mar 10, 2017 at 3:49 PM Doyley, Marvin M. <m.doy...@rochester.edu
> <mailto:m.doy...@rochester.edu>> wrote:
> 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
> --
> Kaushal Modi
>
>
signature.asc
Description: Message signed with OpenPGP using GPGMail
