From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: [BUG][Babel] Exporting text before heading
Date: Fri, 16 Jul 2010 16:12:57 +0200 [thread overview]
Message-ID: <87iq4ffrbq.wl%n.goaziou@gmail.com> (raw)
Hello,
I can't export the following file, would it be to latex or html.
-----
#+TITLE: Title
- First element
#+BEGIN_SRC org
,- one
,- two
#+END_SRC
1. sub-item
#+BEGIN_EXAMPLE
Line 1
Line 2
#+END_EXAMPLE
2. another sub-item
- Another element
-----
If I remove one of the blocks, I can export again to latex or html.
Same thing if I add an heading between the title and the first
element.
If I only add plain text before the first element, or an heading after
the list, it won't work.
I tried to bisect but it appears this org file had never been exported
successfully to html and stopped getting exported successfully to
latex since the following commit:
-----
commit d4781b9d88a6e85c0792e6e24de49834b19b4e57
Author: Carsten Dominik <carsten.dominik@gmail.com>
Date: Fri Jul 9 10:06:17 2010 +0200
Keep BABEL meta lines in tact
* lisp/org-latex.el (org-export-latex-first-lines): Do not mark
meta lines for removal. Do not remove BABEL config lines during export
-----
Because of this, I tend to think it is babel related, even though
removing only the example block also solves the problem.
Config is minimal, so all variables should be at default value, and
the last lines in *Message* buffer are :
-----
Exporting...
org-babel-exp processing...
setf: Wrong type argument: consp, nil
-----
Regards,
-- Nicolas
next reply other threads:[~2010-07-16 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 14:12 Nicolas Goaziou [this message]
2010-07-16 20:02 ` [BUG][Babel] Exporting text before heading Eric Schulte
2010-07-16 20:44 ` Nicolas Goaziou
2010-07-16 22:32 ` Eric Schulte
2010-07-18 6:14 ` Carsten Dominik
2010-07-18 17:06 ` Eric Schulte
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=87iq4ffrbq.wl%n.goaziou@gmail.com \
--to=n.goaziou@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).