Re: [O] bug with LaTeX exporter

2013-06-28 Thread Dennis van Dok
On 28-06-13 04:26, Nick Dokos wrote: Rasmus ras...@gmx.us writes: The old latex exporter was much more finicky about such structure violations: I tried 7.7 (and 7.9.4 to see if it was ever changed) and it does indeed eat the subsubsection. To solve your problem: 1. see if it works as

[O] bug with LaTeX exporter

2013-06-27 Thread Dennis van Dok
Hi, I noticed a bug where a subsubsection without a 'parent' subsection would migrate up into the previous section to end up under the nearest subsection. I tried to make a minimalistic example, but when I export this file to LaTeX, the entire subsubsection disappears! This is emacs24 on Debian

Re: [O] bug with LaTeX exporter

2013-06-27 Thread Rasmus
Hello Dennis, I tried to make a minimalistic example, but when I export this file to LaTeX, the entire subsubsection disappears! Can't reproduce. This is emacs24 on Debian Wheezy, org-mode version 7.7. The current version is 8.0.3. * Bug demonstration This short and simple file

Re: [O] bug with LaTeX exporter

2013-06-27 Thread Nick Dokos
Rasmus ras...@gmx.us writes: Hello Dennis, I tried to make a minimalistic example, but when I export this file to LaTeX, the entire subsubsection disappears! Can't reproduce. This is emacs24 on Debian Wheezy, org-mode version 7.7. The current version is 8.0.3. * Bug demonstration

Re: [O] [BUG] New latex exporter: Not respecting author:nil and timestamp:nil

2012-11-01 Thread Yagnesh Raghava Yakkala
Hello Nicolas, sorry for the late reply. On 10月 20 2012, Nicolas Goaziou n.goaz...@gmail.com wrote: IIUC, there's a mismatch between current behaviour (author:nil = \author{}) and what you want (author:nil = no author command at all). I don't mind switching to the second option if there's

Re: [O] [BUG] New latex exporter: Not respecting author:nil and timestamp:nil

2012-11-01 Thread Nicolas Goaziou
Hello, Yagnesh Raghava Yakkala h...@yagnesh.org writes: It would be good if no author command is export. please implement it. Done. Note: author:nil _and_ email:t will still use the email as the argument of the author command. Regards, -- Nicolas Goaziou

Re: [O] [BUG] New latex exporter: Not respecting author:nil and timestamp:nil

2012-10-20 Thread Nicolas Goaziou
Hello, Yagnesh Raghava Yakkala h...@yagnesh.org writes: #+CAPTION: A wide table with tabulary #+LABEL: tbl:wide It should be #+NAME: tbl:wide Thanks, Manual need to be updated then.. (info (org)Tables in LaTeX export) Manual still applies to /current/ exporter, which is the old one.

[O] [BUG] New latex exporter: Not respecting author:nil and timestamp:nil

2012-10-18 Thread Yagnesh Raghava Yakkala
Hello, New latex exporter doesn't recognize the author:nil and timestamp:nil. test file is attached. #+TITLE: abcd #+AUTHOR: me me #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+OPTIONS: timestamp:nil #+OPTIONS: author:nil #+CAPTION: A wide table with tabulary #+LABEL: tbl:wide

Re: [O] [BUG] New latex exporter: Not respecting author:nil and timestamp:nil

2012-10-18 Thread Nicolas Goaziou
Hello, Yagnesh Raghava Yakkala h...@yagnesh.org writes: New latex exporter doesn't recognize the author:nil and timestamp:nil. test file is attached. #+TITLE: abcd #+AUTHOR: me me #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+OPTIONS: timestamp:nil #+OPTIONS: author:nil

Re: [O] [BUG] New latex exporter: Not respecting author:nil and timestamp:nil

2012-10-18 Thread Yagnesh Raghava Yakkala
Hello Nicolas, On 10月 19 2012, Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, #+CAPTION: A wide table with tabulary #+LABEL: tbl:wide It should be #+NAME: tbl:wide Thanks, Manual need to be updated then.. (info (org)Tables in LaTeX export) #+ATTR_LaTeX: table* tabulary

[O] Bug: new latex exporter, 'Stack overflow in equal' with identical headings

2012-07-16 Thread Myles English
To reproduce: 1. copy the ECM below to a buffer 2. execute the lisp block 3. M-x org-export-dispatch RET l I would expect the orgmode doc to be exported to a latex buffer. What results is an error and the message cdr: Stack overflow in equal bug My setup: started with 'emacs -Q' and with

Re: [O] Bug: new latex exporter, 'Stack overflow in equal' with identical headings

2012-07-16 Thread Nicolas Goaziou
Hello, Myles English mylesengl...@gmail.com writes: To reproduce: 1. copy the ECM below to a buffer 2. execute the lisp block 3. M-x org-export-dispatch RET l I cannot reproduce it but I have pushed a change that may be related to your problem (elements cannot be compared with

Re: [O] Bug: new latex exporter, 'Stack overflow in equal' with identical headings

2012-07-16 Thread Myles English
Hi, Nicolas Goaziou n.goaz...@gmail.com writes: Hello, 1. copy the ECM below to a buffer 2. execute the lisp block 3. M-x org-export-dispatch RET l I cannot reproduce it but I have pushed a change that may be related to your problem (elements cannot be compared with `equal').

Re: [O] [bug?] new latex exporter failing to export

2012-05-21 Thread Bastien
Hi Yagnesh, Yagnesh Raghava Yakkala h...@yagnesh.org writes: I am getting following backtrace when exporting a file to latex (beamer presentation). where as old exporter is working fine. The new exporter is not ready for beamer documents yet. This is one of the prerequisit before making the

[O] [bug?] new latex exporter failing to export

2012-05-20 Thread Yagnesh Raghava Yakkala
Hello, I am getting following backtrace when exporting a file to latex (beamer presentation). where as old exporter is working fine. --8---cut here---start-8--- Debugger entered--Lisp error: (wrong-type-argument stringp nil) string-match(^[

[O] [Bug] New LaTeX exporter ignoring noexport

2012-05-06 Thread Andreas Leha
* Hi all, for me the new latex exporter seems to ignore the :noexport: tag with regard to source block execution. If I export this example, both source blocks get evaluated. (It works well, if I limit the scope of the export to a subtree) ** Do NOT export this

Re: [O] [Bug] New LaTeX exporter ignoring noexport

2012-05-06 Thread Nicolas Goaziou
Hello, Andreas Leha andreas.l...@med.uni-goettingen.de writes: for me the new latex exporter seems to ignore the :noexport: tag with regard to source block execution. If I export this example, both source blocks get evaluated. :noexport: isn't a directive that Babel recognizes. As a

Re: [O] [Bug] New LaTeX exporter ignoring noexport

2012-05-06 Thread Andreas Leha
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: Hello, Andreas Leha andreas.l...@med.uni-goettingen.de writes: for me the new latex exporter seems to ignore the :noexport: tag with regard to source block execution. If I export this example, both source blocks get evaluated.