From: Eric Schulte <schulte.eric@gmail.com>
To: Thomas Holst <thomas.holst@de.bosch.com>
Cc: Bastien <bzg@altern.org>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [bug] org block not correctly exported to LaTeX
Date: Mon, 25 Jul 2011 11:08:33 -0600 [thread overview]
Message-ID: <87tyaajnji.fsf@gmail.com> (raw)
In-Reply-To: <o.ywod4o2ahjoi@de.bosch.com> (Thomas Holst's message of "Mon, 25 Jul 2011 10:02:37 +0200")
Thomas Holst <thomas.holst@de.bosch.com> writes:
> Hi Bastien,
>
> thanks for your answer.
>
>>> when the follwing org-file is exported to LaTeX, #+BEGIN_ORG
>>> and #+END_ORG is inserted in the tex-file.
>>
>> You surely want
>> #+begin_src org
>> #+end_src org
>> "#+begin_org" doesn't exist.
>
> #+BEGIN_ORG
> #+END_ORG
>
> gets inserted by org-babel.
Yes, Babel uses the #+begin/end_org as markers, so that it can identify
the beginning and end of raw Org-mode results when those results need to
be deleted or replaced with new results.
Since these are just used as markers and are functionally equivalent to
comment lines (e.g., no special treatment of the portion between the
begin_org and end_org lines) we didn't really coordinate this with the
results of Org-mode.
It seems however that since comments must start on the first character
of a line, these don't work when indented.
Would it be difficult to recognize these two lines as comments when they
are indented? Note we also have #+begin/end_result lines which may
likely have similar issues.
Best -- Eric
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2011-07-25 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 12:02 [bug] org block not correctly exported to LaTeX Thomas Holst
2011-07-24 23:12 ` Bastien
2011-07-25 8:02 ` Thomas Holst
2011-07-25 17:08 ` Eric Schulte [this message]
2011-07-26 6:50 ` Thomas Holst
2011-07-25 17:48 ` Bernt Hansen
2011-07-26 7:00 ` Thomas Holst
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tyaajnji.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=thomas.holst@de.bosch.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.