From e2745ba306deb895da756bd5dfb74a313395a0e8 Mon Sep 17 00:00:00 2001 From: Eric Schulte Date: Sat, 23 May 2009 08:12:12 -0700 Subject: [PATCH] reorder the tasks by priority --- rorg.org | 44 ++++++++++++++++++++++---------------------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/rorg.org b/rorg.org index 59f28c8e7..19fdac85a 100644 --- a/rorg.org +++ b/rorg.org @@ -5,20 +5,6 @@ * Tasks [17/26] -** TODO command line execution -Allow source code blocks to be called form the command line. This -will be easy using the =sbe= function in [[file:litorgy/litorgy-table.el][litorgy-table.el]]. - -This will rely upon [[* resolve references to other buffers][resolve references to other buffers]]. - -** TODO resolve references to other buffers - This would allow source blocks to call upon tables, source-blocks, - and results in other buffers. - - See... - - [[file:litorgy/litorgy-ref.el::TODO%20allow%20searching%20for%20names%20in%20other%20buffers][litorgy-ref.el:searching-in-other-buffers]] - - [[file:litorgy/litorgy.el::defun%20litorgy%20find%20named%20result%20name][litorgy.el#litorgy-find-named-result]] - ** TODO re-implement R evaluation using ess-command or ess-execute I don't have any complaints with the current R evaluation code or behaviour, but I think it would be good to use the ESS functions @@ -32,6 +18,24 @@ This will rely upon [[* resolve references to other buffers][resolve references commands, or at least articulate under this TODO the reasons for using our custom R-interaction commands. +** TODO resolve references to other buffers + This would allow source blocks to call upon tables, source-blocks, + and results in other buffers. + + See... + - [[file:litorgy/litorgy-ref.el::TODO%20allow%20searching%20for%20names%20in%20other%20buffers][litorgy-ref.el:searching-in-other-buffers]] + - [[file:litorgy/litorgy.el::defun%20litorgy%20find%20named%20result%20name][litorgy.el#litorgy-find-named-result]] + +** TODO figure out how to handle graphic output +This is listed under [[* graphical output][graphical output]] in out objectives. + +This should take advantage of the =:results file= option, and +languages which almost always produce graphical output should set +=:results file= to true by default. That would handle placing these +results in the buffer. Then if there is a combination of =silent= and +=file= =:results= headers we could drop the results to a temp buffer +and pop open that buffer... + ** TODO share litorgy how should we share litorgy? @@ -73,15 +77,11 @@ du -sc ~/* (mapcar #'car sizes) #+end_src -** TODO figure out how to handle graphic output -This is listed under [[* graphical output][graphical output]] in out objectives. +** TODO command line execution +Allow source code blocks to be called form the command line. This +will be easy using the =sbe= function in [[file:litorgy/litorgy-table.el][litorgy-table.el]]. -This should take advantage of the =:results file= option, and -languages which almost always produce graphical output should set -=:results file= to true by default. That would handle placing these -results in the buffer. Then if there is a combination of =silent= and -=file= =:results= headers we could drop the results to a temp buffer -and pop open that buffer... +This will rely upon [[* resolve references to other buffers][resolve references to other buffers]]. ** TODO inline source code blocks [3/5] Like the =\R{ code }= blocks