emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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 14:25:41 -0600	[thread overview]
Message-ID: <87aab2a4vu.fsf@gmail.com> (raw)
In-Reply-To: <87ei0ea5ab.fsf@gmail.com> (Eric Schulte's message of "Sun, 21 Aug 2011 14:17:00 -0600")

Eric Schulte <schulte.eric@gmail.com> writes:

> I've just pushed up a change to org-exp-blocks which should fix Charles'
> original problem related to conflict between inline and regular code
> blocks.  Please let me know if this problem persists in the latest git
> HEAD.
>
> Thanks -- Eric
>
> Eric Schulte <schulte.eric@gmail.com> writes:
>
>> 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)}
>>>

Inline source blocks like those above should now also be exporting as
expected.

Cheers -- Eric

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

  reply	other threads:[~2011-08-21 20:25 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
2011-08-21 20:17     ` Eric Schulte
2011-08-21 20:25       ` Eric Schulte [this message]
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=87aab2a4vu.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).