[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Orgmode] [Babel] Reporting 2 problems of code execution

From: Sébastien Vauban
Subject: [Orgmode] [Babel] Reporting 2 problems of code execution
Date: Sun, 28 Nov 2010 21:04:40 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (windows-nt)

#+TITLE:     2 problems with executing block codes
#+DATE:      2010-11-28

Hi Eric and Dan,

* Abstract

Reporting two problems:

1. parsing problem of unescaped text from a shell block
2. end marker repeated upon execution of elisp block

Note that I added the RESULT thing in my default headers.

* Data

Let's say I want to grep trough arbitrary text, such as:

: He said "I'll do it"
: but that cannot be echo'ed!

... or to let it scanned by AWK for post-processing (like generating some DOT

But, first, as errors are popping up, let's say I can just output it as is.

* Shell code

#+begin_src sh :var data=a-couple-of-lines :exports both
echo "$data"


The data is impossible (*for me*, as is) to print out from a shell code.
Though, it is in Emacs-Lisp... without any change.

Note that it's the second *single quote* only that's causing a problem, not
the first one...

* Emacs-Lisp code

Executing this:

#+begin_src emacs-lisp :var data=a-couple-of-lines :exports both
(prin1-to-string data)

"He said \"I'll do it\"
but that cannot be echoed!"

works, but the *end marker is repeated* as long as we re-execute the block.

Best regards,

Sébastien Vauban

reply via email to

[Prev in Thread] Current Thread [Next in Thread]