a...@ufl.edu (Allen S. Rout) writes:
> "Eric Schulte" writes:
>
>> alternately you could just include your yaml as an example block
>>
>> #+results: yaml-config
>> : erpalpha:...
>
> This is what I've eventually done. It feels dirty; I'm asserting the
> "results" block of a nonexistent src, and
"Eric Schulte" writes:
> alternately you could just include your yaml as an example block
>
> #+results: yaml-config
> : erpalpha:...
This is what I've eventually done. It feels dirty; I'm asserting the
"results" block of a nonexistent src, and saying "edit this". But
perhaps I should just dea
Hi Allen,
Judging from your example org-mode text below I would suggest the
following...
First, the block of yaml is miss-formed, you have a "#+source:" line, and
a "#end_src" line, but you are missing a required "#+begin_src yaml".
Second, if you will be referencing the contents of a yaml code
Greetings.
I've got a YAML config file and some processing I'm doing to it. I'd
love to have both the bits inside the maintenance document I'm writing
to manage a service. This seems a perfect use for code blocks and their
evaluation. However, I get behavior out of my attempt to do this whic
