emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Charles Berry <ccberry@ucsd.edu>
To: emacs-orgmode@gnu.org
Subject: Re: passing the contents of a block as an escaped string
Date: Tue, 24 Jun 2014 16:37:23 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140624T182308-584@post.gmane.org> (raw)
In-Reply-To: m21tueetby.fsf@polytechnique.org

Alan Schmitt <alan.schmitt <at> polytechnique.org> writes:

> 
> Hello,
> 
> I'm trying to write some filters from Pygments, and to record what I'm
> doing and make my life simpler, I'm doing it in an orgmode buffer. In
> that buffer, I have the code I want to highlight in a source block, and
> the python code for the Pygments extension in another block. I'm trying
> to find out how to pass the escaped code from the source to highlight to
> the python buffer.
> 
> I tried using noweb, but the expansion is verbatim and python complains
> about the line breaks. So I'm wondering if there is a way to:
> - pass a source block as an escaped string to another source block, or
> - save a source block to a temporary file, and pass the file name to
> a second source block.
> 


defun a function that formats your src block, then use it in a header

  :var x=(foo "src-block-name")


or maybe wrap (foo ...) in a `format' call or `prin1-to-string' call.


An example is below.

===

Another alternative is to use this idiom (see 14.10 Noweb reference syntax)

   <<code-block-name(optional arguments)>>

where the code-block-name specifies a formatter (in elisp, say) and 
the optional argument is the name of the code block you want to format.

HTH,

Chuck


,----
| #+NAME: prin-block
| #+BEGIN_SRC emacs-lisp :var a="abc" 
|   (defun foo (blk) 
|     (save-excursion
|       (org-babel-goto-named-src-block blk)
|       (nth 1 (org-babel-get-src-block-info 'light))))
| 
| #+END_SRC
| 
| #+NAME: weird-text
| #+BEGIN_SRC python
|   just some plain text;
| 
|   \\ a double slash
| 
|   escape eol \n
|   
|   OK??
| #+END_SRC
| 
| 
| #+BEGIN_SRC python :var a=(foo "weird-text") :results output
| print(a);
| #+END_SRC
| 
| #+RESULTS:
| : just some plain text;
| : 
| : \\ a double slash
| : 
| : escape eol \n
| : 
| : OK??
| 
| #+header: :var a=(prin1-to-string (foo "weird-text")) 
| #+BEGIN_SRC python :results output
| print(a);
| #+END_SRC
| 
| #+RESULTS:
| : "just some plain text;
| : 
| : \\\\ a double slash
| : 
| : escape eol \\n
| : 
| : OK??"
`----

next prev parent reply	other threads:[~2014-06-24 16:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24  6:04 passing the contents of a block as an escaped string Alan Schmitt
2014-06-24 16:37 ` Charles Berry [this message]
2014-06-26  7:27   ` Alan Schmitt

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=loom.20140624T182308-584@post.gmane.org \
    --to=ccberry@ucsd.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

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).