From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Use [org-latex] or [org-e-latex] for exporter problems
Date: Tue, 05 Jun 2012 14:42:27 +0200 [thread overview]
Message-ID: <80d35egcb0.fsf@somewhere.org> (raw)
In-Reply-To: 81vcj6x8pu.fsf_-_@gmail.com
Hi Jambunathan,
Jambunathan K wrote:
> Please use [org-latex] or [org-e-latex] while reporting exporter
> problems. Likewise for other exporters.
This was code for Beamer slides, hence using the old LaTeX exporter.
> If you are exporting with old exporter, export once with the new
> exporter also, just for the fun of it.
Converted the Beamer slideware to a document:
--8<---------------cut here---------------start------------->8---
#+TITLE: Org code in slide
#+DATE: 2012-06-04 Mon
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE: en
#+LaTeX_CLASS: article
#+LaTeX_HEADER: \lstdefinelanguage{org}{%
#+LaTeX_HEADER: morekeywords={:results, :session, :var, :noweb, :exports},
#+LaTeX_HEADER: sensitive=false,
#+LaTeX_HEADER: morestring=[b]",
#+LaTeX_HEADER: morecomment=[l]{\#},
#+LaTeX_HEADER: }
#+LaTeX_HEADER: \lstset{%
#+LaTeX_HEADER: mathescape=false,
#+LaTeX_HEADER: columns=flexible,
#+LaTeX_HEADER: keepspaces=true
#+LaTeX_HEADER: }
* Contexte
- I want to show (in Beamer slides) how to write an Org table.
- I first need to add Org as a language to the listings settings -- that's the
purpose of the above =BEAMER_HEADER_EXTRA= lines.
- I then write an Org source block, which is exported to LaTeX... but not
fully... The line =#+ATTR_LaTeX: align=rrl= disappears from the exported code!
- See ECM.
* ECM
Here's a "simple" but already powerful Org table:
#+begin_src org :exports code
,#+ATTR_LaTeX: align=rrl
,| Janvier | 1300 | \EUR |
,| Fevrier | 1280 | \EUR |
,|---------+------+------|
,| Total | 2580 | \EUR |
,#+TBLFM: @3$2=vsum(@1..@2)
#+end_src
I can't get it properly exported to LaTeX, because the line =ATTR_LaTeX= is
*removed from the published code block* (compare the Org source of the code
block with what's shown in the PDF).
--8<---------------cut here---------------end--------------->8---
- Same problem with the old exporter
- It works with the new one -- but N/A yet for slides; anyway, this is good
news.
> More importantly report problems or inconsistencies. This will immensely
> help to improve the current backends and associated infrastructure.
That, I clearly do (and will still do)...
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-06-05 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 22:17 Problems exporting Org code blocks in LaTeX Sebastien Vauban
2012-06-05 9:05 ` Sebastien Vauban
2012-06-05 12:07 ` Use [org-latex] or [org-e-latex] for exporter problems Jambunathan K
2012-06-05 12:42 ` Sebastien Vauban [this message]
2012-06-05 14:09 ` Jambunathan K
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=80d35egcb0.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).