df6db56a72
now accepting literal values to assign variables in header arguments
2009-05-08 16:20:05 -07:00
cfcff524d0
additional thoughts about passing arguments to source code blocks
2009-05-08 15:38:04 -07:00
9121d6f1f1
now exporting inline source code blocks
2009-04-26 13:29:59 -07:00
1f1ea49ec5
evaluation of inline source blocks working with \C-c\C-c
2009-04-26 11:42:36 -07:00
997c307a92
added additional tasks
2009-04-24 16:48:41 -07:00
d7d2cb6399
updated task and bugs trackers
2009-04-23 15:59:42 -07:00
64e01ac324
fixed bug with exportation of ruby arrays
2009-04-23 15:57:32 -07:00
9652615618
implemented selective export with :exports header argument
...
Acceptable export values are:
both ---- the default, display the code and the results
code ---- display the code inside the block but do not process
results - process the block and replace it with the results of
execution
none ----- do not display either code or results upon export
2009-04-23 15:57:31 -07:00
5d9f00a6db
updating exportation TODO
2009-04-23 15:57:29 -07:00
578a7b9574
Discussion of new TODOs. Couple of additions and a couple of questions
2009-04-17 15:18:21 -07:00
4ba43552c0
new tasks: selective export of code/text, code block folding, interactive session output -> litorgy conversion
2009-04-13 14:37:30 -04:00
54dcc1f4f8
resolved bug mentioned rorg.org
2009-04-05 19:22:50 -07:00
d5bbedbbc0
adding notes to TODOs in rorg.el
2009-04-05 16:27:14 -07:00
f27741e468
now results of shell commands are also converted into tables when appropriate
2009-04-05 10:11:31 -07:00
9bfd6e0a80
now when R blocks return trivial vectors they are converted into scalars
...
Apparently there are no scalars values in R, scalars are packaged into
vectors, which would result in many single element tables
| scalar |
if we just dropped them straight to emacs-lisp without this conversion
2009-04-05 09:46:11 -07:00
834dd2908f
R source blocks can now read in variables from org-mode tables, and insert results as org tables
2009-04-04 16:24:06 -07:00
f8d76eb030
org-R-to-elisp is working
...
it is now able to
1) write the R function to a tab separated table
2) read that table into elisp and return
3) clean up after itself
2009-04-04 16:24:05 -07:00
a9bb21865d
more opining about R tables
2009-04-04 16:24:04 -07:00
3e403fc9bb
R support partially working assigning variables from R
...
still need to figure out how to deal with R tables
2009-04-04 16:24:03 -07:00
0e29fb3601
now assigning variables from source-code blocks in multiple languages
...
Currently ruby, python, and emacs-lisp are working; still need to work
on shells and R.
2009-04-02 20:02:56 -07:00
77c33de593
now able to assign variables from emacs-lisp source blocks
2009-04-02 17:59:55 -07:00
91dea38923
adding TODOs to rorg.org
2009-04-01 15:59:33 -07:00
3657836968
added optional insertion of results...
...
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
2009-04-01 15:46:55 -07:00
e770100002
replaced support for shells
2009-03-31 16:11:41 -07:00
0ca4b60bb6
minor updates to rorg.org
...
fleshing out TODOs
2009-03-31 16:11:40 -07:00
15741e1e69
minor edits to rorg.org
2009-03-31 14:54:19 -04:00
1896489b6a
moved active parts of rorg.org to top, and added bugs section
2009-03-31 10:24:15 -04:00
d8f8161be5
TODO item: evaluation as background process?
2009-03-31 09:51:27 -04:00
d14690e4cf
Merge branch 'master' of git@github.com:eschulte/rorg
2009-03-31 09:49:11 -04:00
fc21c4b559
adding support for R source code blocks
2009-03-29 15:09:06 -07:00
d1230c6ea5
litorgy-script is now functional and plays nice w/matrix output
...
- 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
2009-03-28 19:38:45 -07:00
c814a9f3e8
table assignment now working for ruby and python
2009-03-28 14:49:08 -07:00
17a1d71e6a
Merge branch 'master' of git@github.com:eschulte/rorg
2009-03-26 11:01:46 -04:00
b9dc839e33
added demonstration of the reading/writing of tables to rorg.org
2009-03-25 16:22:27 -07:00
080a1634d7
Merge branch 'master' of git@github.com:eschulte/rorg
2009-03-23 23:42:17 -04:00
74498d6055
thinking about and stubbing out functions for referencing external resources
2009-03-23 17:01:11 -07:00
78c3dc7fb1
Merge branch 'master' of git@github.com:eschulte/rorg
2009-03-05 11:17:09 +00:00
aae046e55e
minor edits, starting to add litorgy-R tasks as they crop up during use
2009-03-05 11:16:45 +00:00
47e18380e9
getting too excited and thinking about distributed computing
2009-03-04 18:14:42 -08:00
2f12591e5a
adding thoughts about referencing data to rorg.org, see
...
**** Eric: referencing data in general
2009-03-04 17:22:28 -08:00
e292e34041
minor additions to rorg.org
2009-02-23 17:58:18 -08:00
715998c107
adding R support for litorgy
2009-02-23 16:08:16 -08:00
a942f75543
adding thoughts about free, explicit, independent variables
2009-02-23 15:15:23 -08:00
f7d0dd1fda
adding a replace option, and simplified result insertion
2009-02-22 22:19:56 -08:00
7c51afb642
Added litorgy.el which begins with the most fundamental step of our
...
implementation, see rorg.org for more information and examples.
2009-02-22 13:19:43 -08:00
a81fe7e15b
some thoughts on referencing data from R
2009-02-12 11:07:25 -05:00
1dd3e1c330
some replies and some interesting scoping discussion from the email
2009-02-11 08:08:34 -08:00
46f6a0a084
Some minor responses
2009-02-10 20:18:20 -05:00
090e5a12ae
small addition to the proposed block format
2009-02-10 14:21:06 -08:00
d26a98d71a
I've done a fairly destructive edit of this file. The main goal was
...
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
2009-02-09 14:43:07 -08:00
ea31e3a9c3
writing overview section at top of rorg.org
2009-02-08 15:00:28 -05:00
cf31c1f134
Trying to write a project overview at top of rorg.org
2009-02-08 13:11:22 -05:00
bdae433d69
I added a couple of things listed below. I happy with the way this is
...
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
2009-02-06 15:45:59 -08:00
0c418c5e2a
rorg.org additions
2009-02-05 21:15:09 -05:00
eeaecdf7ee
merge Eric and Austin's notes on special block types
2009-02-05 20:07:09 -05:00
6201f77b1c
rearrange Eric's notes
2009-02-05 19:59:19 -05:00
f173099443
merge Eric's notes and mine
2009-02-05 19:56:26 -05:00
cf1996f365
explanation and implementation notes for editing R code in org
2009-02-05 19:37:17 -05:00
79ca346be8
adding to rorg.org
2009-02-05 16:00:05 -08:00
a7c75dd901
Filled in more details about first objective.
2009-02-05 18:54:46 -05:00
133b3b9748
Filled in first objective, linked to current implementation.
2009-02-05 18:47:20 -05:00
a3cf89b5b2
initial commit
2009-02-05 15:04:09 -08:00
Eric Schulte
Eric Schulte
Dan Davison
Austin F. Frank