emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Chris Malone <chris.m.malone@gmail.com>
Cc: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: [Babel] The first line of the code blocks disappears in the tangled file
Date: Mon, 13 Dec 2010 13:23:43 -0700	[thread overview]
Message-ID: <87bp4ph168.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTi=N256syJ5GKYK=BAscnPu_irQm8+8kA1_kKApx@mail.gmail.com> (Chris Malone's message of "Wed, 8 Dec 2010 09:24:42 -0500")

I am able to reproduce this error when evaluating a latex code block, so
for example

#+begin_src org :results latex :results replace
  ,- eric
  ,- schulte
#+end_src

#+results:
#+BEGIN_LaTeX
\begin{itemize}
\item schulte
\end{itemize}
#+END_LaTeX

This is due to the fact that org mode code blocks in the presence of
":results latex" or ":results html" will actually convert their contents
to the requested language using Org-mode's export mechanism.  I believe
that in this case the latex exporter wants the first line of the code
block to be used as a title.  I've just pushed up a patch which pads the
first line of org-mode code blocks with an empty title during latex
export.

Best -- Eric

Chris Malone <chris.m.malone@gmail.com> writes:

> Hi Seb,
>
> I can't say that I understand the problem, but I can reproduce it - any line right after the #+begin_src org :results latex is being
> stripped upon tangle.? Not sure if it helps or not, but I'm using org-mode version 7.3 =release_7.3.89.g97f4c.dirty= with emacs
> 22.2.1.
>
> Chris
>
> 2010/12/8 S?bastien Vauban <wxhgmqzgwmuf@spammotel.com>
>
>     #+TITLE: ? ? Isodoc letter (to be tangled to LaTeX file)
>     #+DATE: ? ? ?2010-12-08
>     #+LANGUAGE: ?fr_FR
>    
>     Right now, this letter *must be tangled* and post-processed via =PDFLaTeX=. It
>     can't be exported directly to PDF/HTML (=args out of range= error).
>    
>     The problem I'm reporting here is visible *in the tangled file* (TeX). So, to
>     reproduce it, just do =C-c C-v C-t= on this file, and look at the tangled one.
>    
>     * To
>
> #+begin_src csv :tangle addresses.csv<br>
> FirstName,LastName,Address,PostCode,Town<br>
> Anybody,Kind Enough,to look,at,this<br>
> #+end_src<br>
>
> * Subject
> #+srcname: subject
>
> #+begin_src org :results latex<br>
> This is my subject line<br>
> #+end_src<br>
>
> * Opening
> #+srcname: opening
>
> #+begin_src org :results latex<br>
> Dear,<br>
> #+end_src<br>
>
> * Body
> #+srcname: body
>
> #+begin_src org :results latex<br>
> This example was working for me in the past but is having problems now (at<br>
> least, on my new Windows machine -- after the Ubuntu one died): the first line<br>
> of every block of text is simply eaten when being tangled.<br>
> <br>
> The second paragraph does not exhibit any particular trouble, so it really is<br>
> the first line of every code block. Notice, *in the TeX tangled file*, that:<br>
> <br>
> - the one-liner subject becomes void<br>
> - the one-liner opening becomes void<br>
> - the body looses its first line<br>
> - the one-liner closing becomes void<br>
> #+end_src<br>
>
> * Closing
> #+srcname: closing
>
> #+begin_src org :results latex<br>
> Can you reproduce this?<br>
> #+end_src<br>
>
> * Letter composition
>
> #+begin_src latex :noweb yes :tangle yes<br>
> \documentclass[11pt]{isodoc}<br>
> \usepackage[utf8x]{inputenc}<br>
> \usepackage[T1]{fontenc}<br>
> \usepackage{datatool}<br>
> \DTLloaddb{addresses}{addresses.csv}<br>
> <br>
> \usepackage[scorpios]{isodoc-style}<br>
> <br>
> \setupdocument{<br>
>   subject = {%<br>
>    &lt;&lt;subject()&gt;&gt;},<br>
>   opening = {%<br>
>    &lt;&lt;opening()&gt;&gt;},<br>
>   closing = {%<br>
>    &lt;&lt;closing()&gt;&gt;}<br>
> }<br>
> <br>
> \begin{document}<br>
> \DTLforeach{addresses}{%<br>
>  \firstname=FirstName,%<br>
>  \lastname=LastName,%<br>
>  \addressi=Address,%<br>
>  \postcode=PostCode,%<br>
>  \town=Town%<br>
> }{%<br>
> \letter[to={\firstname~\lastname\\\addressi\\\postcode~\town}]{%<br>
> &lt;&lt;body()&gt;&gt;<br>
> }}<br>
> \end{document}<br>
> #+end_src<br>
>
> Best regards,
> ?Seb
>
> --
> S?bastien Vauban
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-12-13 20:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 12:46 [Babel] The first line of the code blocks disappears in the tangled file Sébastien Vauban
2010-12-08 14:24 ` Chris Malone
2010-12-13 20:23   ` Eric Schulte [this message]
2010-12-16 13:05     ` Sébastien Vauban

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=87bp4ph168.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=chris.m.malone@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.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 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).