Yes, perfect!
On Mon, Apr 14, 2014 at 6:35 AM, Oleh wrote:
> Hi Phil,
>
> Could you test my last commit? Your case should be working now.
>
> regards,
> Oleh
>
I am getting a strange effect from ":results pp" and ob-clojure. "It\n
looks\n like\n this.\n" I built Emacs 24.4.50 from trunk and cloned
ob-clojure from git today. clojure-mode is 20140331 from ELPA. cider is
20140411 from ELPA.
Two examples follow.
1. uses =:results pp= ("and\n looks\n lik
ob-clojure.el should use separate cider functions for value and output
results, in order to avoid expressing standard output as some kind of
programming-language string with embedded \n notation. I experimentally
adjusted my copy of ob-clojure (obtained from git clone -b master today)
like this:
How can a Clojure source block contribute its standard-output results as an
example block? I tried ":results output org" but it expressed the standard
output as a quoted string with \n's where I expected newlines. For a point
of comparison, org-python seems to be able to do what I want, if "begin
How may I use an Org document to illustrate Clojure src blocks that produce
Clojure data structures -- particularly maps -- as pretty-printed text? I
think I am using Org "master" in Emacs 24.3.
#+BEGIN_SRC clojure :results value <>
(zipmap
["Peru" "Paris" "Sankt-Peterburg" "Philadelphia" "Plat
It is better. To really stress it, I tried a two-row table:
#+begin_src clojure :results table
[[:ny :nj :ct]
[ 7 9 4]]
#+end_src
#+RESULTS:
| :ny | :nj | :ct |
| 7 | 9 | 4 |
On Wed, Jan 29, 2014 at 10:28 AM, Bastien wrote:
> Eric Schulte writes:
>
> > Try evaluating the fol