From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jacob Gerlach Subject: Toggling Macro Definition Date: Sun, 21 Sep 2014 22:09:23 -0400 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b3a84be8b74eb05039df07b Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34642) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XVt4F-0006Y1-9C for emacs-orgmode@gnu.org; Sun, 21 Sep 2014 22:09:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XVt4E-0003jo-9e for emacs-orgmode@gnu.org; Sun, 21 Sep 2014 22:09:31 -0400 Received: from mail-la0-x230.google.com ([2a00:1450:4010:c03::230]:35407) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XVt4E-0003jc-1n for emacs-orgmode@gnu.org; Sun, 21 Sep 2014 22:09:30 -0400 Received: by mail-la0-f48.google.com with SMTP id ty20so5772117lab.21 for ; Sun, 21 Sep 2014 19:09:24 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --047d7b3a84be8b74eb05039df07b Content-Type: text/plain; charset=UTF-8 After writing a detailed report in org-mode and submitting it via latex/pdf, I've found out that for the next version of the report, I am required to use "track changes" in MS Word. I thought my best way to approximate this is to submit two versions: one with removed text in strikeout and new text in red (hence my previous post where I learned to RTFM on Macro arguments). The best hack I could think of to generate a "final" pdf was to change the macro definition so that struckout text isn't included in the output and new text is no longer red. i.e. #+MACRO: stk @@latex:\sout{$1}@@ becomes #+MACRO: stk This works for body text, but leaves an empty headline, and in general I don't really like it. Do any experienced org-folk have recommendations on a better way to do this? --047d7b3a84be8b74eb05039df07b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
After writing a detailed report in org-mode and submitting= it via latex/pdf, I've found out that for the next version of the repo= rt, I am required to use "track changes" in MS Word.

I thought my best way to approximate this is to submit two versions:= one with removed text in strikeout and new text in red (hence my previous = post where I learned to RTFM on Macro arguments).

= The best hack I could think of to generate a "final" pdf was to c= hange the macro definition so that struckout text isn't included in the= output and new text is no longer red.

i.e.
<= div>
#+MACRO: stk @@latex:\sout{$1}@@
becomes
=
#+MACRO: stk

This works for body text, bu= t leaves an empty headline, and in general I don't really like it. Do a= ny experienced org-folk have recommendations on a better way to do this?
--047d7b3a84be8b74eb05039df07b--