a...@ufl.edu (Allen S. Rout) writes: > "Eric Schulte" <schulte.e...@gmail.com> 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 deal with it. > > Am I silly to want to be able to label it 'srcname' instead of > 'results'? My elisp-fu is not good enough to let me define > > :var-but-read-the-src-block >
These are just labels, and more than that they are just the labels that first occurred to Dan and I. Semantically they are used to name data, and I can understand your "dirty" feeling of having results without a related code block, but rest assured, Babel does not assume that there should exist such a code block and this sort of usage is both supported and intended. To emphasize this point, I've just pushed up a change so that you can now label such inline data with #+data: my-named-data : 3 and more importantly you can add your own labels by customizing the new `org-babel-data-names' variable. Cheers -- Eric n Note: if you update the `org-babel-data-names' variable you might want to later run the following code... (setq org-babel-result-regexp (concat "^[ \t]*#\\+" (regexp-opt org-babel-data-names) "\\(\\[\\([[:alnum:]]+\\)\\]\\)?\\:[ \t]*")) > > - Allen S. Rout > > > -- Eric Schulte http://cs.unm.edu/~eschulte/