From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Allen S. Rout" <asr@ufl.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: PERL, org-mode and literal document input.
Date: Fri, 06 May 2011 14:55:18 -0600 [thread overview]
Message-ID: <87y62jtupr.fsf@gmail.com> (raw)
In-Reply-To: 87liyjwpfl.fsf@ufl.edu
asr@ufl.edu (Allen S. Rout) writes:
> "Eric Schulte" <schulte.eric@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/
prev parent reply other threads:[~2011-05-06 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 20:25 PERL, org-mode and literal document input Allen S. Rout
2011-05-05 17:19 ` Eric Schulte
2011-05-06 20:21 ` Allen S. Rout
2011-05-06 20:55 ` Eric Schulte [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y62jtupr.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=asr@ufl.edu \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).