emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Ista Zahn <istazahn@gmail.com>
To: Lawrence Bottorff <borgauf@gmail.com>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Latex export or Latex tangle? Best practice?
Date: Mon, 27 Apr 2015 14:34:31 -0400	[thread overview]
Message-ID: <CA+vqiLGosHWdVfAFyo78RY2LZvXNwN32aHdV_VzVBr-GDMvEoA@mail.gmail.com> (raw)
In-Reply-To: <CAFAhFSUO84tgY5qqw0PVR_pXiVkkmZFWWPK+9BJcvnGhhnQfSQ@mail.gmail.com>

I would use LaTeX code blocks when I need to write something in LaTeX
that isn't easy to write in org mode, not to distinguish what is a
note and what is part of the draft. For that I recommend comments,
e.g.,


### Start example ###

* Section 1
** COMMENT Some rough draft notes to myself
 yadda yadda more badda
** Some stuff that should be exported
This is the actual important stuff that should be exported
*** More stuff that should be exported
yadda yada
*** COMMENT More notes and stuff don't export
*** Export this one too
bla bla

### End example ###

When you export the commented sections will be excluded.

Best,
Ista
On Mon, Apr 27, 2015 at 2:12 PM, Lawrence Bottorff <borgauf@gmail.com> wrote:
> In a previous post I was getting at the issue of whether I should just do
> regular export or use latex "code blocks" for what I wanted in a final
> document. What I want is the ability to create a big, rambling, annotated
> org file -- with "keeper" stuff inside the latex babel blocks -- then tangle
> the .org file, thereby leaving all the annotations and lead-up notes behind.
> I'm sure I'm not alone in wanting "notes" to evolve into a "finished
> product" and orgmode would seem to offer a good path. So, I don't want to
> have to hand-edit out my so-called annotations. Is keeping the good stuff in
> latex babel blocks a best practice?
>
> LB

next prev parent reply	other threads:[~2015-04-27 18:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 18:12 Latex export or Latex tangle? Best practice? Lawrence Bottorff
2015-04-27 18:34 ` Ista Zahn [this message]
2015-04-28  3:06 ` Charles C. Berry

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=CA+vqiLGosHWdVfAFyo78RY2LZvXNwN32aHdV_VzVBr-GDMvEoA@mail.gmail.com \
    --to=istazahn@gmail.com \
    --cc=borgauf@gmail.com \
    --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

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).