emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Lawrence Bottorff <borgauf@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Latex export or Latex tangle? Best practice?
Date: Mon, 27 Apr 2015 14:12:53 -0400	[thread overview]
Message-ID: <CAFAhFSUO84tgY5qqw0PVR_pXiVkkmZFWWPK+9BJcvnGhhnQfSQ@mail.gmail.com> (raw)

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

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

[-- Attachment #2: Type: text/html, Size: 731 bytes --]

             reply	other threads:[~2015-04-27 18:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 18:12 Lawrence Bottorff [this message]
2015-04-27 18:34 ` Latex export or Latex tangle? Best practice? Ista Zahn
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=CAFAhFSUO84tgY5qqw0PVR_pXiVkkmZFWWPK+9BJcvnGhhnQfSQ@mail.gmail.com \
    --to=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
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).