all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Henry Blevins <heblevi@gmail.com>
To: Neil Jerram <neil@ossau.homelinux.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ob-scheme.el: Fix scheme blocks ignoring :results in formatting
Date: Thu, 21 Jun 2018 14:44:04 -0400	[thread overview]
Message-ID: <CABO_LAmSx+MrdC48LJKpcpvo0jTk-8Ki4ya1pG_G+vK2DdoEqQ@mail.gmail.com> (raw)
In-Reply-To: <871sd0dnw2.fsf@ossau.homelinux.net>

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

Neil Jerram <neil@ossau.homelinux.net> writes:

> But if I want the table output
>
> | 1 | 2 | 3 |
>
> will there still be a way to get it? (I'm sure I have org files that
> need this!)

This patch will not affect any of your existing org files unless you have
specified you want the block to output as 'verbatim', 'scalar' or
otherwise. For
all org source blocks the default is to process the output as a table if it
is
in a suitable format, so the following would still occur:

#+BEGIN_SRC scheme
  (list 1 2 3)
#+END_SRC

#+RESULTS:
| 1 | 2 | 3 |

Additionally, you can always specify the output be processed as a table by
specifying it in the ':results' header argument.

#+BEGIN_SRC scheme :results table
  (list 1 2 3)
#+END_SRC

#+RESULTS:
| 1 | 2 | 3 |

The other defined options for result formatting can be found here
https://orgmode.org/manual/results.html.

[-- Attachment #2: Type: text/html, Size: 2169 bytes --]

      reply	other threads:[~2018-06-21 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20 19:36 [PATCH] ob-scheme.el: Fix scheme blocks ignoring :results in formatting Henry Blevins
2018-06-21 16:16 ` Nicolas Goaziou
2018-06-21 19:05   ` Henry Blevins
2018-06-21 20:02     ` Nicolas Goaziou
2018-06-21 17:56 ` Neil Jerram
2018-06-21 18:44   ` Henry Blevins [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABO_LAmSx+MrdC48LJKpcpvo0jTk-8Ki4ya1pG_G+vK2DdoEqQ@mail.gmail.com \
    --to=heblevi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=neil@ossau.homelinux.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.