From: Phill Wolf <phill.wolf@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Soapy Smith <soapy-smith@comcast.net>,
emacs-orgmode@gnu.org, Christian Moe <mail@christianmoe.com>,
Eric Schulte <schulte.eric@gmail.com>
Subject: Re: Clojure Code Block Results not Tabularized
Date: Wed, 29 Jan 2014 18:40:04 -0500 [thread overview]
Message-ID: <CAH+qJsJE4z3YB8_nhTVUDWYOQNbEJBcsSnJCMRQZLYCGFYWREg@mail.gmail.com> (raw)
In-Reply-To: <87r47qrenk.fsf@bzg.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
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 <bzg@gnu.org> wrote:
> Eric Schulte <schulte.eric@gmail.com> writes:
>
> > Try evaluating the following and see how it works.
>
> It works fine for me:
>
> ,----
> | #+BEGIN_SRC clojure :results table
> | (map #(* %1 3) '(1 2 3))
> | #+END_SRC
> |
> | #+RESULTS:
> | | 3 | 6 | 9 |
> `----
>
> > This simply copies
> > the results handling from the slime backend to the cider backend (which
> > currently does not appear to have any results handling). While you're
> > at it the nrepl results handling looks broken to me as well.
>
> Yep.
>
> Greg, please test Eric's function above for all your use cases and let
> us know if it covers them all -- then I'll fix this and the nrepl case
> too.
>
> Thanks Eric!
>
> --
> Bastien
>
>
[-- Attachment #2: Type: text/html, Size: 1591 bytes --]
next prev parent reply other threads:[~2014-01-29 23:40 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
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 [this message]
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=CAH+qJsJE4z3YB8_nhTVUDWYOQNbEJBcsSnJCMRQZLYCGFYWREg@mail.gmail.com \
--to=phill.wolf@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.com \
--cc=schulte.eric@gmail.com \
--cc=soapy-smith@comcast.net \
/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).