emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Austin Frank <austin.frank@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: possible latex export bug
Date: Sun, 12 Oct 2008 23:56:01 -0400	[thread overview]
Message-ID: <m0myh9no6m.fsf@gmail.com> (raw)
In-Reply-To: 91445AC9-0690-4BE1-80FE-D078EBB234A0@uva.nl


[-- Attachment #1.1: Type: text/plain, Size: 1929 bytes --]

On Fri, Oct 10 2008, Carsten Dominik wrote:

> I believe this bug has been fixed recently by Bastien.  Could you
> please check and confirm that this is the case?

Carsten and Bastien--

I still get this behavior.  To reproduce

1.  Start emacs with emacs -Q
2.  Evaluate the line

  (require 'org-install)

3.  Open a new file, tesing.org.  Execute M-x org-mode.
4.  Put the following content in testing.org

--8<---------------cut here---------------start------------->8---

* test
#+BEGIN_LATEX
\begin{verbatim}
a <- 3
\end{verbatim}
#+END_LATEX
--8<---------------cut here---------------end--------------->8---

5.  Execute org-export-as-latex by C-c C-e l
6.  Output is

--8<---------------cut here---------------start------------->8---
% Created 2008-10-12 Sun 23:43
\documentclass[11pt,a4paper]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{hyperref}


\title{testing}
\author{Austin Frank}
\date{12 October 2008}

\begin{document}

\maketitle

\setcounter{tocdepth}{3}
\tableofcontents


\section{test}
\label{sec-1}

\begin{verbatim}
a <- 3
\end{verbatim}
#+END_LATEX


\end{document}
--8<---------------cut here---------------end--------------->8---


I also am seeing that file-local variables at the bottom of the file are
still exported into the latex.  For now I'm assuming that it's the same
bug, but if the #+END_LATEX bug gets fixed and the other persists, I'll
file another report :)

Org-mode version 6.09a
GNU Emacs 23.0.60.1 (powerpc-apple-darwin8.11.0, *Step 9.0) of
2008-10-12

Just to be sure, I also ran

  git diff origin lisp/org-exp.el
  git diff origin lisp/org-export.el

and found no differences between my local copy and the copy in the
origin repository.  I think that's the right way to check, but feel free
to correct me if I'm comparing things incorrectly.

Thanks,
/au

--
Austin Frank
http://aufrank.net
GPG Public Key (D7398C2F): http://aufrank.net/personal.asc

[-- Attachment #1.2: Type: application/pgp-signature, Size: 193 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2008-10-13  3:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02  9:15 possible latex export bug Austin Frank
2008-10-02 15:07 ` Manish
2008-10-10 21:13 ` Carsten Dominik
2008-10-13  3:56   ` Austin Frank [this message]
2008-10-14 18:46     ` Carsten Dominik
2008-10-15  2:54       ` Austin Frank
2008-10-15 11:06         ` Carsten Dominik

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=m0myh9no6m.fsf@gmail.com \
    --to=austin.frank@gmail.com \
    --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).