From: Frozenlock <frozenlock@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [BUG] ORG-LIST-END-MARKER when exporting from within a babel block with an exclude or include tag
Date: Mon, 16 Jan 2012 00:01:19 -0500 [thread overview]
Message-ID: <CACjB3dt9ObrQYYa9Z5oO-NVZ3=n+wYGuawED=m0+wtpVos1EsQ@mail.gmail.com> (raw)
Ok, I know this a very specific application. Perhaps it's not even a
bug and I'm using it the wrong way.
Here is a minimum working example:
----------------------------------------------------
#+TITLE: Test org file
#+EXPORT_INCLUDE_TAGS: test2
* First heading :test1:
Testing, 1-2, 1-2.
* Second heading :test2:
Because we can.
** Now a list
- First item
- Second item
#+BEGIN_SRC emacs-lisp :results raw :exports results :var
buffer-file-name=(buffer-file-name)
(let ((org-export-babel-evaluate nil)); don't evaluate in 'recursive' exports
(org-export-as-ascii org-export-headline-levels))
#+END_SRC
----------------------------------------------------
If you export this file to PDF (C-c C-e d), babel will evaluate and
export the file as ascii. However, the ascii file will have the
undesirable "ORG-LIST-END-MARKER" in it.
Here is the resulting ascii export:
----------------------------------------------------
Test org file
=============
Author:
Date: 2012-01-15 23:51:47
Table of Contents
=================
1 First heading
2 Second heading
2.1 Now a list
1 First heading :test1:
-----------------------
Testing, 1-2, 1-2.
2 Second heading :test2:
------------------------
Because we can.
2.1 Now a list
===============
- First item
- Second item
ORG-LIST-END-MARKER
----------------------------------------------------
Any idea on how to fix this?
next reply other threads:[~2012-01-16 5:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 5:01 Frozenlock [this message]
2012-01-16 15:18 ` [BUG] ORG-LIST-END-MARKER when exporting from within a babel block with an exclude or include tag 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='CACjB3dt9ObrQYYa9Z5oO-NVZ3=n+wYGuawED=m0+wtpVos1EsQ@mail.gmail.com' \
--to=frozenlock@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).