From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Lawrence Bottorff <borgauf@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Latex export or Latex tangle? Best practice?
Date: Mon, 27 Apr 2015 20:06:18 -0700 [thread overview]
Message-ID: <alpine.OSX.2.00.1504271954001.1313@charles-berrys-macbook.local> (raw)
In-Reply-To: <CAFAhFSUO84tgY5qqw0PVR_pXiVkkmZFWWPK+9BJcvnGhhnQfSQ@mail.gmail.com>
On Mon, 27 Apr 2015, Lawrence Bottorff 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
>
I sometimes use noweb references for the purpose of having either a
concise code block to tangle or a document for export that draws on code
blocks elsewhere in the document.
From what I see higher in this thread, I recommend that you export a
subtree that includes src blocks with noweb refs. Whatever latex
boilerplate you need can be :EXPORT_*: properties. see
(info "(org) Noweb reference syntax")
and the paragraphs at the end of
(info "(org) Export settings")
HTH,
Chuck
prev parent reply other threads:[~2015-04-28 3:06 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
2015-04-28 3:06 ` Charles C. Berry [this message]
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=alpine.OSX.2.00.1504271954001.1313@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--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
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).