[O] [bug] [new exporter] export of inline babel calls confused
Hello,
in trying to see if I could replicate a problem with disappearing src
code blocks, I have run into problems with the new exporter. The
attached minimal example generates a very strange convoluted latex
output (also attached).
The old exporter doesn't do a perfect job but comes a lot closer!
Thanks,
eric
--
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.2-568-gc2ebee
% Created 2012-11-08 Thu 09:43
\documentclass{scrartcl}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage[integrals]{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\usepackage{xcolor}
\usepackage{listings}
\usepackage{amsmath}
\providecommand{\alert}[1]{\textbf{#1}}
\title{examplebug.org}
\author{Eric S Fraga}
\date{\today}
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Emacs Org-mode version 7.9.2}}
\begin{document}
\maketitle
\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}
\section{disappearing source code blocks}
\label{sec-1}
The following source code block counts the number of files in the current directory.
\begin{verbatim}
375
\end{verbatim}
There are =375
= files in the directory.
\end{document}
# -*- org-confirm-babel-evaluate: nil; -*-
#+TITLE: examplebug.org
#+AUTHOR:Eric S Fraga
* disappearing source code blocks
The following source code block counts the number of files in the current directory.
#+name: t1
#+begin_src sh :exports results :results output
# count the number of files in the directory
ls | wc -l
#+end_src
There are call_t1() files in the directory.
Re: [O] [bug] [new exporter] export of inline babel calls confused
Apologies! I attached the latex file generated by the old exporter
instead of the one generated by the new one.
Here is the latex generated by the new exporter (I hope ;-).
Thanks,
eric
--
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.2.50.1 and Org release_7.9.2-568-gc2ebee
% Created 2012-11-08 Thu 09:48
\documentclass{scrartcl}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage[integrals]{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\usepackage{xcolor}
\usepackage{listings}
\usepackage{amsmath}
\author{Eric S Fraga}
\date{\today}
\title{examplebug.org}
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Generated by Org mode 7.9.2 in Emacs 24.2.50.1.}}
\begin{document}
\maketitle
\tableofcontents
\vspace*{1cm}
=379
=* disappearing source code blocks
The following source code block counts the number of files in the current directory.
\begin{verbatim}
379
\end{verbatim}
Ther$_\mathrm{t1}$() files in the directory.
% Generated by Org mode 7.9.2 in Emacs 24.2.50.1.
\end{document}
Re: [O] [bug] [new exporter] export of inline babel calls confused
Hello, Eric S Fraga writes: > in trying to see if I could replicate a problem with disappearing src > code blocks, I have run into problems with the new exporter. The > attached minimal example generates a very strange convoluted latex > output (also attached). After a quick glance, it looks like point is moved to the wrong place (it is moved to the headline whereas it should stay near the call) in either `org-babel-exp-src-block' or `org-babel-in-export-file'. You can eval the following snippet to see what is really parsed: (let ((org-current-export-file (current-buffer))) (org-export-block-preprocess)) I'm Cc'ing Eric Schulte in case he finds time to look at the problem. Regards, -- Nicolas Goaziou
Re: [O] [bug] [new exporter] export of inline babel calls confused
Hello, Eric S Fraga writes: > in trying to see if I could replicate a problem with disappearing src > code blocks, I have run into problems with the new exporter. The > attached minimal example generates a very strange convoluted latex > output (also attached). > > The old exporter doesn't do a perfect job but comes a lot closer! This bug should be squashed. Thank you for reporting it. Regards, -- Nicolas Goaziou
