From: cberry@tajo.ucsd.edu
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] new exporter and #+BEGIN_CENTER
Date: Tue, 17 Jul 2012 20:52:08 -0700 [thread overview]
Message-ID: <877gu1915j.fsf@tajo.ucsd.edu> (raw)
In-Reply-To: 81ipdmymkk.fsf@gmail.com
Jambunathan K <kjambunathan@gmail.com> writes:
> Center within Src. I don't think you can nest the blocks.
>
It seems you are right. At least as far as executing the src block is concerned.
I was thinking along the lines of LaTeX's center environment, but I see
now that a src block within a CENTER didn't work with the old exporter
either.
> The cryptic message is org-export.el way of saying that there is a parse
> error or that the Org file doesn't to conform to schema.
The latest git pull gives no error - it just doesn't run the src block.
>
>> This throws an error:
>>
>> ------------------------------
>> * headline 1
>>
>> #+BEGIN_CENTER
>>
>> #+BEGIN_SRC R :exports both
>> rnorm(10)
>> #+END_SRC
>>
>> #+END_CENTER
>> ------------------------------
>>
>> M-: (org-export-to-buffer 'e-latex "latex buffer") RET
>>
>> It does not run the src block and the error is:
>>
>> (error "Invalid search bound (wrong side of point)")
>> re-search-forward("@@[-A-Za-z0-9]+:" 31 t)
>> [snip]
>> org-element-export-snippet-successor(31)
>> [rest deleted]
>>
>> Removing the whitespace between the BEGIN_CENTER and BEGIN_SRC lines
>> runs, but wrongly fails to execute the src block.
>>
>> Removing the CENTER results in running the src block and producing the
>> expected result.
>>
>> My last pull was yesterday: b7be665..69af091
>>
>> HTH,
>>
>> Chuck
--
Charles C. Berry Dept of Family/Preventive Medicine
cberry at ucsd edu UC San Diego
http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
next prev parent reply other threads:[~2012-07-18 3:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 23:31 [BUG] new exporter and #+BEGIN_CENTER cberry
2012-07-17 23:45 ` Nicolas Goaziou
2012-07-17 23:50 ` Jambunathan K
2012-07-18 3:52 ` cberry [this message]
2012-07-18 7:56 ` Nicolas Goaziou
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=877gu1915j.fsf@tajo.ucsd.edu \
--to=cberry@tajo.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).