From: "Michaël Cadilhac" <firstname.lastname@example.org>
To: ian martins <email@example.com>
Cc: Org-Mode mailing list <firstname.lastname@example.org>
Subject: Re: Why is Babel-C trimming its output?
Date: Fri, 17 Jul 2020 12:30:30 -0500 [thread overview]
Message-ID: <CADt3fpPofOUXvrdUNDLJUPKsGTzP9xZ2K1MG9yEonikhbTG03Q@mail.gmail.com> (raw)
Thanks for the investigation Ian. So, since the tests run just fine
without it, and it offers an inconsistent and at times detrimental
feature, can we consider removing it, and/or adding some options for
I'd be fine having to flag my src-block with a ":verbatim t" option to
make sure that the output is not mangled.
On Fri, Jul 17, 2020 at 7:30 AM ian martins <email@example.com> wrote:
> Fortunately the author wrote tests, so we can tie the behavior of the code to use cases. Unfortunately all the tests pass with the call to org-trim removed. Also the call is there from the first commit of the file in git, so there's no commit message to explain.
> My guess is that it was added to clean up cases that resulted in extra trailing whitespace, but I dunno.
> On Wed, Jul 15, 2020 at 7:12 PM Michaël Cadilhac <firstname.lastname@example.org> wrote:
>> Quick question here: in ob-C.el, before returning the output of a C
>> file, there's this line:
>> (setq results (org-trim (org-remove-indentation results)))
>> That seems quite arbitrary; is it on purpose? I have a C file that
>> outputs some sort of list of formatted numbers, e.g.:
>> 0 -17.8
>> 40 4.4
>> 80 26.7
>> 120 48.9
>> and only the first line gets trimmed, leading to a faulty output.
>> This does not seem to be a universal thing in Babel; for instance:
>> #+begin_src emacs-lisp :exports both :results value raw
>> " 0\n 1\n2\n"
>> …results in:
>> But the same thing in C:
>> #+begin_src C :exports both :results output raw
>> printf (" 0\n 1\n2\n");
>> …results in:
next prev parent reply other threads:[~2020-07-17 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 23:12 Why is Babel-C trimming its output? Michaël Cadilhac
2020-07-17 12:30 ` ian martins
2020-07-17 17:30 ` Michaël Cadilhac [this message]
2020-07-25 15:18 ` ian martins
2020-09-04 10:13 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).