emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: "Charles C. Berry" <ccberry@ucsd.edu>, "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>, eschulte@cs.unm.edu
Subject: Re: Preventing RESULTS from being formatted as org table [ob-awk]
Date: Mon, 13 Jun 2016 14:12:43 +0000	[thread overview]
Message-ID: <CAFyQvY0mpS8hhDEKk3wtpX6yq0AfmBajPakxVpbOCWdx67EFFw@mail.gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.20.1606121302340.831@charles-berrys-macbook.local>

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

Hi Charles, Thomas,

Thank you for the replies. They were very useful.

I learned about :post for the first time. That minimal example worked
great. Earlier I was confused about "*this*", but then from Info node
"(org) post", I learned that it's a special variable for :post.

For now, ":results verbatim" does the job for me for awk source blocks. But
:post looks like a very powerful generic solution. With your reply, I at
least tried it out and I will keep that in mind for when I might need to
use it in future.

Kaushal

On Sun, Jun 12, 2016 at 5:02 PM Charles C. Berry <ccberry@ucsd.edu> wrote:

> TL;DR: That is almost correct. `:post' header arg gives fine control of
> formatting if needed.
>
> `org-babel-insert-result' formats anything that isn't a string or a list
> using "%S". Then it tries hard to turn a list into a "table". Lists that
> cannot be made into tables are formatted as strings with "%s\n". However,
> various languages have their own formatting principles, so what
> `org-babel-insert-result' gets as the `result' is a bit idiosyncratic.
>
> You can get a deeper look at the `result' by pretty printing it with the
> aid of a :post header arg. Example:
>
>
> #+NAME: I-feel-pretty
> #+BEGIN_SRC emacs-lisp :results pp
> *this*
> #+END_SRC
>
> This elisp list is not revised:
>
> #+BEGIN_SRC emacs-lisp :post I-feel-pretty
> '(a b c (d . e))
> #+END_SRC
>
> #+RESULTS:
> : (a b c
> :    (d . e))
>


> On Sun, 12 Jun 2016, Thomas S. Dye wrote:
>  I think I'm correct to say that by default a single value result is
>  output as a scalar, and everything else is converted to an Org mode
>  table.
>
-- 

-- 
Kaushal Modi

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

      reply	other threads:[~2016-06-13 14:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-12  6:46 Preventing RESULTS from being formatted as org table [ob-awk] Kaushal Modi
2016-06-12  6:59 ` Kaushal Modi
2016-06-12  7:05   ` Kaushal Modi
2016-06-12 16:30     ` Kaushal Modi
2016-06-12 18:22       ` Thomas S. Dye
2016-06-12 18:41         ` Kaushal Modi
2016-06-12 19:29           ` Thomas S. Dye
2016-06-12 21:02             ` Charles C. Berry
2016-06-13 14:12               ` Kaushal Modi [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

  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=CAFyQvY0mpS8hhDEKk3wtpX6yq0AfmBajPakxVpbOCWdx67EFFw@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=ccberry@ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=eschulte@cs.unm.edu \
    --cc=tsd@tsdye.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).