emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thomas Holst <thomas.holst@de.bosch.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Cc: "Holst Thomas (DGS-EC/ESE4)" <Thomas.Holst@de.bosch.com>,
	Bastien <bzg@altern.org>
Subject: Re: [bug] org block not correctly exported to LaTeX
Date: Mon, 25 Jul 2011 10:02:37 +0200	[thread overview]
Message-ID: <o.ywod4o2ahjoi@de.bosch.com> (raw)
In-Reply-To: <87zkk3tgry.fsf@gnu.org> (bzg@altern.org's message of "Mon, 25 Jul 2011 01:12:17 +0200")

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. Here is the relevant part of ob.el lines
1620 ff.

#+srcname: ob.el
#+begin_src emacs-lisp
  ;; ....
  ((member "org" result-params)
   (wrap "#+BEGIN_ORG" "#+END_ORG"))
  ;; ...
#+end_src emacs-lisp

Here is an example which shows the issue.

#+begin_src org
* Testing org-babel perl
  
  #+srcname: TestingPerl
  #+begin_src perl :exports results :results output org
    print("#+CAPTION: A caption\n");
    print("#+LABEL: tbl:dvi\n");
    print("#+ATTR_LaTeX: placement[H]\n");
    print("| *bold/T* |\n");
    print("|--------|\n");
    print("| normal |\n");
  #+end_src

  #+results: TestingPerl
  #+BEGIN_ORG
  #+CAPTION: A caption
  #+LABEL: tbl:dvi
  #+ATTR_LaTeX: placement[H]
  | *bold/T* |
  |--------|
  | normal |
  #+END_ORG
#+end_src org

I tested replacing 

 #+BEGIN_ORG 
 #+END_ORG 

with 

 #+BEGIN_SRC org
 #+END_SRC org

But that doesn't work. The org-babel output is inserted verbatim when
exported to LaTeX. That is not what is expected. 

I could use a

:results output raw

header, but with a long output (including blank lines) org-babel has
problems finding the end of the output when recalculating the source
block. The org-babel output gets appended not rewritten.

My workaround is not indenting the source block. Then everything works
as expected. But indented soure blocks look nicer.

Thanks again for looking into this.
-- 
Mit freundlichen Grüßen / Best regards 

Thomas Holst 
DGS-EC/ESE4

Tel.   +49 (711) 811-40681
PC-Fax +49 (711) 811-5182208

  reply	other threads:[~2011-07-25  8:03 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 [this message]
2011-07-25 17:08     ` Eric Schulte
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

  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=o.ywod4o2ahjoi@de.bosch.com \
    --to=thomas.holst@de.bosch.com \
    --cc=bzg@altern.org \
    --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).