from the description of litorgy-insert-result:
Insert RESULT into the current buffer after the end of the
current source block. With optional argument INSERT controls
insertion of results in the org-mode file. INSERT can take the
following values...
t ------ the default options, simply insert the results after the
source block
replace - insert results after the source block replacing any
previously inserted results
silent -- no results are inserted
- litorgy-script no longer handles shell scripts
- litorgy-script now inserts the *return value* of the source block,
rather than inserting what was printed to STDOUT
- now able to handle table output from ruby and python source blocks
to enforce a structure on the document that we can use moving forward,
so that any future objective changes are all made to the main
objective list.
I apologize for removing sections written by other people. I did this
when they were redundant or it was not clear how to fit them into this
structure. Rest assured if the previous text wasn't persisted in git
I would have been much more cautious about removing it.
I hope that this outline structure should be able to remain stable
through the process of fleshing out objectives, and cashing those
objectives out into tasks. That said, please feel free to make any
changes that you see fit.
Changes include...
- tearing stuff out, and imposing structure
- updated .gitignore to ignore exported files
progressing so far. It's nice to work on a project where everyone
uses org-mode.
additions:
- proposal for how we should implement the R-source-code blocks
- example of source code evaluation using org-eval-light.el
- notes section on evaluation of R code
- some scattered thoughts/suggestions
Eric Schulte
Dan Davison
Austin F. Frank