Revising bugs and tasks in org-babel.org

This commit is contained in:
Dan Davison 2009-07-18 14:02:22 -04:00
parent 24927c2a45
commit cfb9092ede

View file

@ -199,11 +199,18 @@ would then be [[#sandbox][the sandbox]].
#+end_src
* Tasks [30/49]
* Tasks [30/50]
** PROPOSED optional timestamp for output
Add option to place an (inactive) timestamp at the #+resname, to
record when that output was generated.
** PROPOSED use example block for large amounts of stdout output?
We're currently `examplizing' with : at the beginning of the line,
but should larger amounts of output be in a
\#+begin_example...\#+end_example block? What's the cutoff? > 1 line?
\#+begin_example...\#+end_example block? What's the cutoff? > 1
line? This would be nice as it would allow folding of lengthy
output. Sometimes one will want to see stdout just to check
everything looks OK, and then fold it away.
** TODO make tangle files read-only?
With a file-local variable setting, yea that makes sense. Maybe
the header should reference the related org-mode file.
@ -664,76 +671,6 @@ This would allow for display of images upon export providing
functionality similar to =org-exp-blocks= only in a more general
manner.
** TODO Add languages [1/6]
I'm sure there are many more that aren't listed here. Please add
them, and bubble any that you particularly care about up to the top.
Any new language should be implemented in a org-babel-lang.el file.
Follow the pattern set by [[file:lisp/org-babel-script.el][org-babel-script.el]], [[file:lisp/org-babel-shell.el][org-babel-shell.el]] and
[[file:lisp/org-babel-R.el][org-babel-R.el]].
*** TODO perl
This could probably be added to [[file:lisp/org-babel-script.el][org-babel-script.el]]
*** TODO java
*** DONE ditaa
(see [[* file result types][file result types]])
#+srcname: implementing-ditaa
#+begin_src ditaa :results replace :file blue.png :cmdline -r
+---------+
| cBLU |
| |
| +----+
| |cPNK|
| | |
+----+----+
#+end_src
#+resname: implementing-ditaa
[[file:blue.png][blue.png]]
*** STARTED gnuplot
(see [[* file result types][file result types]])
- a =file= header argument
- a =cmdline= header argument
- to add variables
- scalar variables should be replaced in the body of the gnuplot code
- vector variables should be exported to tab-separated files, and
the variable names should be replaced with the path to the files
#+PLOT: title:"Citas" ind:1 deps:(3) type:2d with:histograms set:"yrange [0:]"
#+TBLNAME: gnuplot-data
| independent var | first dependent var | second dependent var |
|-----------------+---------------------+----------------------|
| 0.1 | 0.425 | 0.375 |
| 0.2 | 0.3125 | 0.3375 |
| 0.3 | 0.24999993 | 0.28333338 |
| 0.4 | 0.275 | 0.28125 |
| 0.5 | 0.26 | 0.27 |
| 0.6 | 0.25833338 | 0.24999993 |
| 0.7 | 0.24642845 | 0.23928553 |
| 0.8 | 0.23125 | 0.2375 |
| 0.9 | 0.23333323 | 0.2333332 |
| 1 | 0.2225 | 0.22 |
| 1.1 | 0.20909075 | 0.22272708 |
| 1.2 | 0.19999998 | 0.21458333 |
| 1.3 | 0.19615368 | 0.21730748 |
#+srcname: implementing-gnuplot
#+begin_src gnuplot :var data=gnuplot-data
set title "Implementing Gnuplot"
plot "data" using 1:2 with lines
#+end_src
*** TODO dot
(see [[* file result types][file result types]])
*** TODO asymptote
(see [[* file result types][file result types]])
** DEFERRED use textConnection to pass tsv to R?
When passing args from the org buffer to R, the following route is
used: arg in buffer -> elisp -> tsv on file -> data frame in R. I
@ -2055,7 +1992,7 @@ This could probably be added to [[file:lisp/org-babel-script.el][org-babel-scrip
+----+----+
#+end_src
#+resname:
#+resname: implementing-ditaa
[[file:blue.png][blue.png]]
*** STARTED gnuplot
@ -2100,12 +2037,14 @@ plot "data" using 1:2 with lines
* Bugs [19/30]
** TODO o-b-execute-subtree overwrites some buffer contents
*** Try M-x org-babel-execute-subtree with point at the beginning of this line
** TODO o-b-execute-subtree overwrites heading when subtree is folded
*** Example
Try M-x org-babel-execute-subtree with the subtree folded and
point at the beginning of the heading line.
#+begin_src sh
b=2
size=5
#+end_src
** 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
@ -2178,7 +2117,13 @@ the same for the other languages. [Dan]
inserting the results (after possible further recursive calls to
org-babel-ref-resolve-reference), point hasn't gone back to the
lob line.
** TODO LoB: output to buffer adds creeping blank lines
** TODO creeping blank lines
There's still inappropriate addition of blank lines in some circumstances. E.g.
#+begin_src sh
b=5
#+end_src
Compare the results of
#+lob: python-add(a=5, b=17)