From: tsd@tsdye.com (Thomas S. Dye)
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Bug in export of call lines
Date: Tue, 11 Mar 2014 20:00:05 -1000 [thread overview]
Message-ID: <m2k3c06joa.fsf@tsdye.com> (raw)
In-Reply-To: <8738iokoxy.fsf@gmail.com> (Eric Schulte's message of "Tue, 11 Mar 2014 19:40:27 -0600")
Eric Schulte <schulte.eric@gmail.com> writes:
> I think it is allowable for raw results to include newlines. After if R
> returns a newline, the purpose of raw results is specifically to *not*
> change the result. I believe the best approach is to customize the
> inline results wrap as above, and then use non-raw processed results
> when inline results without newlines are desired.
>
> Does this sound reasonable?
I'm able to export my document correctly by removing :results raw from
the R source code blocks.
I can control wrapping of the results by making the calls :results raw,
which removes the wrap.
I don't see any change in newline behavior by changing
org-babel-inline-result-wrap.
Unlike your shell block, I don't get an extraneous newline.
I only see unexpected behavior with R source code blocks when :results
raw is set at the source code block.
The following tables summarize what I'm seeing.
* Tables of results :noexport:
With "%s", modified value of org-babel-inline-result-wrap
#+name: R-results
| | call raw | call not raw |
|----------------+------------+----------------------|
| source raw | newline | verbatim and newline |
| source not raw | no newline | no newline |
#+name sh-results
| | call raw | call not raw |
|----------------+------------+--------------|
| source raw | no newline | no newline |
| source not raw | no newline | no newline |
With "=%s=", the default value of org-babel-inline-result-wrap
#+name: R-results-default
| | call raw | call not raw |
|----------------+------------+---------------------------------|
| source raw | newline | verbatim and newline, no texttt |
| source not raw | no newline | no newline, texttt |
#+name sh-results-default
| | call raw | call not raw |
|----------------+------------+--------------------|
| source raw | no newline | no newline, texttt |
| source not raw | no newline | no newline, texttt |
I'll dig deeper tomorrow to see why my shell source code blocks don't
behave as yours do. In any case, my document exports again.
Thanks,
Tom
--
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
prev parent reply other threads:[~2014-03-12 6:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 2:05 Bug in export of call lines Thomas S. Dye
2014-03-10 12:16 ` Nicolas Goaziou
2014-03-10 17:14 ` Thomas S. Dye
2014-03-10 17:38 ` Eric Schulte
2014-03-11 2:45 ` Thomas S. Dye
2014-03-11 13:23 ` Eric Schulte
2014-03-11 21:50 ` Thomas S. Dye
2014-03-12 1:40 ` Eric Schulte
2014-03-12 6:00 ` Thomas S. Dye [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=m2k3c06joa.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=schulte.eric@gmail.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).