Re: [O] Python Code Block error with header option :results output

I'm not a Python expert too but I don't that return statement can be used as is on the fly. So, yes is the expected behavior of Python Try instead #+begin_src python :results output a = (1, 2, 3, 4) print(a) #+end_src #+RESULTS: : (1, 2, 3, 4) On Fri, Jan 31, 2014 at 9:24 PM, Soapy Smith

Re: [O] How to use ox-bibtex

You can also use latexmkwhich was designed to solve this kind of problem. I have this in my init.el (setq org-latex-pdf-process '("latexmk -pdflatex=xelatex -pdf -latexoption=-shell-escape %f")) On Wed, Jan 29, 2014 at 2:46 PM, Ni

Re: [O] Proposal/request for input: slidify export for html slides

I love slidify too and I think that having similar functionnality in org could be great. I think that you have everything to do that using the html backend, you just need to interface the right Javascript/HTML5 library. In slidify you can use io2012, deck.js, shower and landslide and I know that yo

Re: [O] Different behavior of exported results in org-babel

deletions of the source code blocks (possibly putting them back again > > if the header args tell it to) but it does not always delete the right > > region. More details later. > > Indeed. I pushed a fix that should, hopefully, solve the issue. > > Thanks to Ahmadou Dicko for

Re: [O] Different behavior of exported results in org-babel

Thanks for testing. As a workaround I will use your trick (in buffer evaluation before exporting) but I was thinking of writing a filter. On Fri, Jan 17, 2014 at 7:04 PM, Nick Dokos wrote: > Ahmadou Dicko writes: > > > Hi everyone, > > > > I use the latest version

[O] Different behavior of exported results in org-babel

Hi everyone, I use the latest version of org-mode (from github) and I update it daily. I noticed some changes recently in org-babel (ob-R). Here's a sample code to explain the problem : #+TITLE: Test export #+AUTHOR: Ahmadou H. DICKO #+PROPERTY: session *R* #+PROPERTY: cache yes #+PROPERTY: expo