emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Daniel Mescheder <mail@danielmescheder.de>
To: emacs-orgmode@gnu.org
Subject: Bug: Latex export fails when src block contains "[X]" [7.7]
Date: Sun, 13 Nov 2011 00:54:37 +0000	[thread overview]
Message-ID: <E1RPOLQ-00082f-Ai@eggs.gnu.org> (raw)


Hi,

I'm running the following system:

Emacs  : GNU Emacs 23.2.1 (i686-pc-linux-gnu, GTK+ Version 2.24.4)
 of 2011-04-04 on rothera, modified by Debian
Package: Org-mode version 7.7

I've run into a problem with #+begin_src #+end_src blocks:
Whenever I trying to have a one-element python list inside of such a block the pdf-export will fail with 

(wrong-type-argument stringp nil)

Here comes a minimal example:

------------------------------------
* Some section

This works fine:

#+begin_src python
    print [0,1,2]
#+end_src

This does not work:

#+begin_src python
    print [1]
#+end_src
------------------------------------

(For some reason I needed to include the src-block in some section. 
That is probably an unrelated problem.)

The trace of this example is

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  string-match("ORG-LIST-END-MARKER\\'" nil)
  org-export-latex-preprocess((:emph-multiline t :for-backend latex :comments nil :tags not-in-toc :priority nil :footnotes t :drawers nil :timestamps t :todo-keywords t :tasks t :add-text nil :skip-before-1st-heading nil :select-tags ("export") :exclude-tags ("noexport") :LaTeX-fragments nil))
  org-export-preprocess-string(#("* Some section\n\nThis works fine:\n\n#+begin_src python\n    print [0,1,2]\n#+end_src\n\nThis does not work:\n\n#+begin_src python\n    print [1]\n#+end_src\n\n" 0 18 (font-lock-fontified t fontified nil) 18 19 (font-lock-fontified t fontified nil) 19 20 (fontified nil) 20 22 (fontified nil) 22 34 (fontified nil) 34 35 (fontified nil) 35 36 (fontified nil) 36 53 (fontified nil) 53 54 (fontified nil) 54 72 (fontified nil font-lock-fontified t) 72 73 (fontified nil font-lock-fontified t) 73 77 (fontified nil font-lock-fontified t) 77 90 (fontified nil font-lock-fontified t) 90 91 (fontified nil font-lock-fontified t) 91 100 (fontified nil font-lock-fontified t) 100 101 (fontified nil font-lock-fontified t) 101 102 (fontified nil font-lock-fontified t) 102 1
 21 (fontified nil font-lock-fontified t) 121 122 (fontified nil font-lock-fontified t) 122 123 (fontified nil font-lock-fontified t) 123 141 (font-lock-fontified t fontified nil) 141 142 (font-lock-fontified t fontified nil) 142 146 (font-lock-fontified t fontified nil) 146 155 (font-lock-fontified t fontified nil) 155 156 (font-lock-fontified t fontified nil) 156 164 (font-lock-fontified t fontified nil) 164 165 (font-lock-fontified t fontified nil rear-nonsticky t) 165 166 (fontified nil font-lock-fontified t) 166 167 (fontified nil)) :emph-multiline t :for-backend latex :comments nil :tags not-in-toc :priority nil :footnotes t :drawers nil :timestamps t :todo-keywords t :tasks t :add-text nil :skip-before-1st-heading nil :select-tags ("export") :exclude-tags ("noexport") :LaTeX-fragme
 nts nil)
  org-export-as-latex(nil nil nil nil nil nil)
  org-export-as-pdf(nil)
  call-interactively(org-export-as-pdf)
  org-export(nil)
  call-interactively(org-export nil nil)


I don't want to exclude the possibility that this has to do with my particular setup.
If you cannot reproduce this problem, I'll have a look whether there's anything relevant in my config files.

Regards,
Daniel

next             reply	other threads:[~2011-11-13  0:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-13  0:54 Daniel Mescheder [this message]
2011-11-13  8:42 ` Bug: Latex export fails when src block contains "[X]" [7.7] Nicolas Goaziou

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=E1RPOLQ-00082f-Ai@eggs.gnu.org \
    --to=mail@danielmescheder.de \
    --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

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).