Hi David, I agree we would like to allow more control over the appearance of exported code blocks. Since this patch admits better control over the format of name and arguments of code blocks on export, could you include a couple of example customizations along with their results?
I've just applied this patch to my system, and although it works in most cases, it raises an error when exporting the following subtree to html --8<---------------cut here---------------start------------->8--- ** lob -- writing results out to files #+source: table #+begin_src emacs-lisp (mapcar (lambda (el) (number-sequence el (+ el 3))) (number-sequence 0 4)) #+end_src writes the results out as csv file #+call: write(data=table, file="~/Desktop/example.csv") :results silent writes the results out as tab separated file #+call: write(data=table, file="~/Desktop/example.tsv") :results silent write the results out as a normal org-mode file #+call: write(data=table, file="~/Desktop/example.org") :results silent --8<---------------cut here---------------end--------------->8--- Cheers -- Eric "David O'Toole" <dto1...@gmail.com> writes: > I've attached a diff of my apparently-working changes to allow better > control of the way ob-exp.el formats the name and arguments of source > code blocks. > > What do you think? > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
