Also an interesting approach!
I never execute src blocks on export though (old habit of having
expensive blocks, and the desire to know what the export looks like).
This is close to what I want:
#+name: el_attr
#+BEGIN_SRC emacs-lisp :var data='(1 2 3)
(org-babel-format-result
(concat
"#+tbln
On Sat, 21 Nov 2015, John Kitchin wrote:
I am running a search committee of 5 people. As applications come in, an
org heading is created for each application, and I run a command to send
one of the committee an email with a review rubric in it, and this
command creates a subheading to put their
I am running a search committee of 5 people. As applications come in, an
org heading is created for each application, and I run a command to send
one of the committee an email with a review rubric in it, and this
command creates a subheading to put their review. We have 275
applications so far, so
John,
Just curious. What advantage do you see in adding these attributes to the code
block, and not directly to the result?
Vikas
> On 21-Nov-2015, at 11:34 pm, John Kitchin wrote:
>
> Thanks. That gets me pretty close to what I want.
>
> Charles C. Berry writes:
>
>> On Sat, 21 Nov 2015,
Thanks. That gets me pretty close to what I want.
Charles C. Berry writes:
> On Sat, 21 Nov 2015, John Kitchin wrote:
>
>> Hi everyone,
>>
>> I am trying to figure out a way to automatically add some attributes to
>> tables generated from code blocks.
>>
>
> With ob-org loaded:
>
> #+BEGIN_SRC em
On Sat, 21 Nov 2015, John Kitchin wrote:
Hi everyone,
I am trying to figure out a way to automatically add some attributes to
tables generated from code blocks.
With ob-org loaded:
#+BEGIN_SRC emacs-lisp
(require 'ob-org)
#+END_SRC
this src block (n.b. there is a backslash escaped n in the
