From: Soapy Smith <soapy-smith@comcast.net>
To: Christian Moe <mail@christianmoe.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Clojure Code Block Results not Tabularized
Date: Wed, 29 Jan 2014 07:36:28 -0500 [thread overview]
Message-ID: <1390998988.2272.12.camel@raven-CM5571> (raw)
In-Reply-To: <m2y51zkynz.fsf@uio.no>
Hi Christian, I think that is a very good point!
From the manual, the explanation of what is returned as a result
using :results raw
"raw The results are interpreted as raw Org mode code and are inserted
directly into
the buffer. If the results look like a table they will be aligned as
such by Org mode.
E.g., :results value raw."
So, it doesn't say it will result in a table, but it will be aligned
like a table!
Whatever the case, the behavior of Clojure should be consistent with the
other languages.
Looking into the "old" set further, I find the :results header argument
makes no difference:
:results value
:results value raw
:results table
(no header argument)
All result in the same org table. So it looks like the old version was
not behaving properly either. However, it was able to coerce the
Clojure vector into an org table successfully.
With the new system (version 8 org and CIDER),
there are in fact 3 different results blocks:
(no header argument)
#+RESULTS:
: [1 2 3 4]
:results value raw
#+RESULTS:
[1 2 3 4]
:results value
#+RESULTS:
: [1 2 3 4]
:results table
#+RESULTS:
| [1 2 3 4] |
Christian, could you try :results table with Python and reply back with
the #+RESULTS:?
Regards,
Greg
On Wed, 2014-01-29 at 08:57 +0100, Christian Moe wrote:
> Hi,
>
> I don't use Clojure so I may get this wrong, but: isn't this what you
> would expect with `:results raw'?
>
> Cf. these Python examples:
>
> #+begin_src python :results raw
> a = (1, 2, 3)
> return a
> #+end_src
>
> #+RESULTS:
> (1, 2, 3)
>
> #+begin_src python
> a = (1, 2, 3)
> return a
> #+end_src
>
> #+RESULTS:
> | 1 | 2 | 3 |
>
> Yours,
> Christian
next prev parent reply other threads:[~2014-01-29 12:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 13:41 How to use ox-bibtex o.castillo.felisola
2014-01-26 18:02 ` Eric Schulte
2014-01-26 19:37 ` o.castillo.felisola
2014-01-27 13:52 ` o.castillo.felisola
2014-01-27 14:36 ` Eric Schulte
2014-01-28 8:32 ` Rainer M Krug
2014-01-28 9:04 ` Christian Moe
2014-01-28 10:08 ` Rainer M Krug
2014-01-28 12:38 ` Rainer M Krug
2014-01-28 15:19 ` o.castillo.felisola
2014-01-29 2:16 ` Eric Schulte
2014-01-29 14:16 ` o.castillo.felisola
2014-01-29 14:46 ` Nick Dokos
2014-01-30 10:02 ` Ahmadou Dicko
2014-01-28 12:33 ` o.castillo.felisola
2014-01-28 12:01 ` Rainer M Krug
2014-01-28 13:23 ` Clojure Code Block Results not Tabularized Soapy Smith
2014-01-29 7:57 ` Christian Moe
2014-01-29 12:36 ` Soapy Smith [this message]
2014-01-29 12:58 ` Christian Moe
2014-01-29 13:06 ` Soapy Smith
2014-01-29 15:02 ` Eric Schulte
2014-01-29 15:28 ` Bastien
2014-01-29 23:40 ` Phill Wolf
2014-01-30 11:11 ` Bastien
2014-01-30 13:46 ` Soapy Smith
2014-01-31 1:58 ` Soapy Smith
2014-01-31 9:11 ` Bastien
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=1390998988.2272.12.camel@raven-CM5571 \
--to=soapy-smith@comcast.net \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.com \
/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).