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 <borg...@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