From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eric Schulte" Subject: Re: PERL, org-mode and literal document input. Date: Fri, 06 May 2011 14:55:18 -0600 Message-ID: <87y62jtupr.fsf@gmail.com> References: <87ei4gc0kg.fsf@ufl.edu> <87vcxouauw.fsf@gmail.com> <87liyjwpfl.fsf@ufl.edu> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:40534) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QIS3k-000871-FI for emacs-orgmode@gnu.org; Fri, 06 May 2011 16:55:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QIS3j-0007ZZ-Ah for emacs-orgmode@gnu.org; Fri, 06 May 2011 16:55:36 -0400 Received: from mail-pv0-f169.google.com ([74.125.83.169]:36441) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QIS3j-0007ZA-6B for emacs-orgmode@gnu.org; Fri, 06 May 2011 16:55:35 -0400 Received: by pvc12 with SMTP id 12so2276761pvc.0 for ; Fri, 06 May 2011 13:55:33 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Allen S. Rout" Cc: emacs-orgmode@gnu.org asr@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 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/