From: Eric Schulte <schulte.eric@gmail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
"Charles C. Berry" <ccberry@ucsd.edu>
Subject: Re: [babel] [bug] inline src_R breaks downstream src block
Date: Sun, 21 Aug 2011 12:35:51 -0600 [thread overview]
Message-ID: <87pqjya9yw.fsf@gmail.com> (raw)
In-Reply-To: <87ty9d3tj5.fsf@gnu.org> (Bastien's message of "Sat, 20 Aug 2011 00:50:38 +0200")
Bastien <bzg@altern.org> writes:
> Hi Charles,
>
> yes, there are some problems with parsing inline source blocks.
> Stephen also reported that these colon lines
>
> : were $\beta_2$ = src_R{round(out3$coef[3], 4)}
> : and $\beta_3$ = src_R{round(out3$coef[4], 4)}
>
> where not exporting correctly... Eric, can you have a look at
> these problems?
>
> Thanks!
>
It will probably be a couple of days before I have sufficient time to
address these issues, but rest assured it is only my TODO list.
Thanks -- Eric
>
> "Charles C. Berry" <ccberry@ucsd.edu> writes:
>
>> ,----
>> | | * inline code block example
>> | | | AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
>> | blah blah src_R[:results output]{cat(rnorm(2))}
>> | CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
>> | #+begin_src R :eval never :exports none
>> | 1+2
>> | a <- b + c
>> | xyz
>> | #+end_src
>> | DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD
>> `----
>>
>>
>> When I run C-c C-e A y, I get a buffer that misses the 'DDD...' line.
>>
>> When I run C-c C-e L y, I get a buffer that ends like this:
>>
>> ----
>> | AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
>> | blah blah \texttt{-1.172165 -0.5324113}
>> | CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
>> | \begin{src}R DDDDDDDDDDDDDDDDDDDDDDDDDDD
>> | | \end{document}
>> `----
>>
>> More complicated examples exhibit other problems, I speculate that
>> parsing the inline src_R and setting up to find the next
>> #+begin_src...#+end_src instance is what has gone wrong.
>>
>> FWIW, changing the :exports header to 'code' seems to give correct
>> results
>>
>> Also, placing a dummy example like this:
>>
>> ,----
>> | #+begin_example
>> | #+end_example
>> `----
>>
>> after the src_R line produces correct results.
>>
>> Chuck
>>
>>
>> Charles C. Berry Dept of Family/Preventive Medicine
>> cberry@tajo.ucsd.edu UC San Diego
>> http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
>>
>>
>>
>>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2011-08-21 18:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 4:00 [babel] [bug] inline src_R breaks downstream src block Charles C. Berry
2011-08-19 22:50 ` Bastien
2011-08-21 18:35 ` Eric Schulte [this message]
2011-08-21 20:17 ` Eric Schulte
2011-08-21 20:25 ` Eric Schulte
2011-08-22 3:19 ` Charles C. Berry
2011-08-22 14:25 ` Eric Schulte
2011-08-22 17:32 ` Charles C. Berry
2011-08-22 19:58 ` Rasmus
2011-08-22 20:08 ` Eric Schulte
2011-08-23 16:27 ` Bastien
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=87pqjya9yw.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=bzg@altern.org \
--cc=ccberry@ucsd.edu \
--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).