From 37569346f82afa31edccc7a8bbbe69a6fcce0dee Mon Sep 17 00:00:00 2001 From: Eric Schulte Date: Mon, 6 Jul 2009 19:36:44 -0700 Subject: [PATCH] stole a couple of moments to add discussion and a new TODO --- org-babel.org | 42 ++++++++++++++++++++++++++++++++++-------- 1 file changed, 34 insertions(+), 8 deletions(-) diff --git a/org-babel.org b/org-babel.org index 869fb587e..56a6d1b52 100644 --- a/org-babel.org +++ b/org-babel.org @@ -1,5 +1,5 @@ #+TITLE: org-babel --- facilitating communication between programming languages and people -#+SEQ_TODO: TODO PROPOSED STARTED | DONE DEFERRED REJECTED +#+SEQ_TODO: PROPOSED TODO STARTED | DONE DEFERRED REJECTED #+OPTIONS: H:3 num:nil toc:t #+STARTUP: oddeven hideblocks @@ -190,7 +190,7 @@ would then be [[#sandbox][the sandbox]]. #+end_src -* Tasks [27/42] +* Tasks [27/43] ** TODO support for working with =*Org Edit Src Example*= buffers [2/4] *** TODO optionally evaluate header references when we switch to =*Org Edit Src*= buffer That seems to imply that the header references need to be evaluated @@ -322,6 +322,17 @@ languages which almost always produce graphical output should set 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 =\C-c \C-o= to open results of source block +by adding a =defadvice= to =org-open-at-point= we can use the common +=\C-c \C-o= keybinding to open the results of a source-code block. +This would be especially useful for source-code blocks which generate +graphical results and insert a file link as the results in the +org-mode buffer. (see [[* figure out how to handle graphic output][TODO figure out how to handle graphic output]]). +This could also act reasonably with other results types... + +- file :: use org-open-at-point to open the file +- scalar :: open results unquoted in a new buffer +- tabular :: export the table to a new buffer and open that buffer ** TODO Finalise behaviour regarding vector/scalar output *** DONE Stop spaces causing vector output @@ -1912,20 +1923,18 @@ This could probably be added to [[file:lisp/org-babel-script.el][org-babel-scrip (see [[* file result types][file result types]]) -* Bugs [17/24] +* Bugs [17/23] ** TODO Allow source blocks to be recognised when #+ are not first characters on the line I think Carsten has recently altered the core so that #+ can have preceding whitespace, at least for literal/code examples. org-babel should support this. -** PROPOSED make :results replace the default? +** TODO make :results replace the default? I'm tending to think that appending results to pre-existing results creates mess, and that the cleaner `replace' option should be the default. E.g. when a source block creates an image, we would want that to be updated, rather than have a new one be added. -** PROPOSED external shell execution can't isolate return values -I have no idea how to do this as of yet. The result is that when -shell functions are run w/o a session there is no difference between -the =output= and =value= result arguments. + + I agree. ** TODO non-orgtbl formatted lists for example @@ -1958,6 +1967,23 @@ even a third" E.g. the pie chart example. Despite the save-window-excursion in org-babel-execute:R. (I never learned how to do this properly: org-R jumps all over the place...) + +** PROPOSED external shell execution can't isolate return values +I have no idea how to do this as of yet. The result is that when +shell functions are run w/o a session there is no difference between +the =output= and =value= result arguments. + +Yea, I don't know how to do this either. I searched extensively on +how to isolate the *last* output of a series of shell commands (see +[[* last command for + shells][last command for shells]]). The results of the search were basically +that it was not possible (or at least not accomplish-able with a +reasonable amount of effort). + +That fact combined with the tenancy to all ways use standard out in +shell scripts led me to treat these two options (=output= and =value=) +as identical in shell evaluation. Not ideal but maybe good enough for +the moment. ** DEFERRED weird escaped characters in shell prompt break shell evaluation E.g. this doesn't work. Should the shell sessions set a sane prompt