From: Eric Schulte <schulte.eric@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: babel results handling
Date: Wed, 03 Apr 2013 08:18:09 -0600 [thread overview]
Message-ID: <87r4irwsoy.fsf@gmail.com> (raw)
In-Reply-To: 20130401162204.GA89231@BigDog.local
Rick Frankel <rick@rickster.com> writes:
> On Sun, Mar 31, 2013 at 07:37:38AM -0600, Eric Schulte wrote:
>> It is certainly true that Emacs Lisp is treated differently than all
>> other languages. There are also significant differences between
>> languages, e.g., session evaluation doesn't make sense for some
>> languages, and for other languages session evaluation is the only type
>> of evaluation that does make sense.
>>
>> In addition to that, with over 40 supported languages [1], There
>> undoubtedly are cases where we are doing a bad job of ensuring
>> inter-languages consistency. If you can find concise examples which use
>> demonstrate significant inconsistencies between languages, then we
>> should be able to resolve those on a case by case basis. In general I
>> think ob-sh is probably the most widely used code block language, and
>> can be treated as the gold standard against which other languages should
>> be compared.
>
> `sh' is probably not the best choice as a "gold standard" due to the
> fact that it only supports STDOUT ("output" and not "value").
>
> Many of the languages are obviously not general purpose, or do not
> support (like shell), wrapped values (only STDOUT), or don't generate
> text, so consistency does not matter (e.g., css, sass, sql, sqlite,
> plantuml, dot).
>
> Regardless, the attached org file is a first step an comparing the
> result processing of some languages (specifically, sh, emacs-lisp,
> perl and ruby), which, I think, covers a good portion of the babel use
> of general purpose languages.
>
This is a great file. Thanks for generating it and sharing it.
Although I think it would be more useful if languages were the smallest
scale of organization rather than the largest to make cross-language
comparison easier.
Would it be difficult to add another set of code blocks which
automatically compare the output of these automatically generated code
blocks, indicating when there are differences.
>
> The upshot, is that perl value results match shell value/output
> results and emacs-lisp, python and ruby all return about the same
> results (elisp returns the quote characters from a verbatim string).
>
What are the perl-shell vs. python-ruby-elisp differences?
>
> I still think that the scalar pipe-delimited processing from shell and
> perl is wrong in that pipe-delimited data ends up w/ an extra column
> if each line starts w/ a pipe, but not if the pipe is used like a
> csv separator (between columns but not at the beginning or end of the
> line).
>
If you want to use pipes to delimit data, then I'd suggest *not*
interpreting the data as a value, but rather doing something like
":results verbatim drawer". Generally pipes aren't considered to be
table column delimiters, I'd try tabs or spaces instead.
>
> Also, looking at the manual
> (http://orgmode.org/manual/results.html#results) vs. the code, are
> there are actually four classes of :results arguments with type broken
> into type and format?
>
> - Type :: (file list vector table scalar verbatim)
> - Format :: (raw html latex org code pp drawer)
>
Yes, this does seem to be more clear. If you're willing to supply a
documentation patch I'd be very happy to apply it.
Thanks!
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2013-04-03 15:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 1:46 [PATCH] Process hlines in imported tables Rick Frankel
2013-03-29 15:04 ` Eric Schulte
2013-03-29 21:42 ` Rick Frankel
2013-03-30 0:01 ` Eric Schulte
2013-03-30 23:41 ` Rick Frankel
2013-03-31 0:43 ` Eric Schulte
2013-03-31 12:29 ` Rick Frankel
2013-03-31 13:37 ` Eric Schulte
2013-04-01 16:22 ` babel results handling (was: Process hlines in imported tables) Rick Frankel
2013-04-03 14:18 ` Eric Schulte [this message]
2013-04-03 18:02 ` babel results handling Achim Gratz
2013-04-04 18:20 ` Rick Frankel
2013-04-03 18:21 ` [PATCH] Process hlines in imported tables Achim Gratz
2013-04-04 13:59 ` Sebastien Vauban
2013-04-04 15:02 ` Eric Schulte
2013-04-04 21:01 ` Sebastien Vauban
2013-04-06 16:30 ` Eric Schulte
2013-04-15 13:06 ` Sebastien Vauban
2013-04-15 15:25 ` Eric Schulte
2013-04-15 19:27 ` Sebastien Vauban
2013-04-04 18:35 ` Rick Frankel
2013-04-04 21:05 ` Sebastien Vauban
2013-04-04 19:29 ` Achim Gratz
2013-04-06 16:29 ` Eric Schulte
2013-04-06 17:07 ` Eric Schulte
2013-04-06 17:24 ` Bastien
2013-04-06 17:39 ` Eric Schulte
2013-04-04 18:30 ` Rick Frankel
2013-04-04 20:27 ` Sebastien Vauban
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=87r4irwsoy.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).