From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: [bug] [new-exporter] #+includes in non-exported regions do not work
Date: Sun, 28 Oct 2012 10:42:26 +0000 [thread overview]
Message-ID: <87mwz63mjx.fsf@ucl.ac.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]
Hello,
with an up to date org, I cannot get the attached minimal example to
export using the new exporter. I have try exporting to latex-pdf, in
case that matters. The (line-length truncated) error trace is:
--8<---------------cut here---------------start------------->8---
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
file-readable-p(nil)
(not (file-readable-p file))
(cond ((not (file-readable-p file)) (error "Cannot include file %s" file))
(let* ((value (match-string 1)) (ind (org-get-indentation)) (file (and (st
(progn (beginning-of-line) (let* ((value (match-string 1)) (ind (org-get-i
(if (eq (org-element-type (save-match-data (org-element-at-point))) (quote
(when (eq (org-element-type (save-match-data (org-element-at-point))) (quo
(while (re-search-forward "^[ ]*#\\+INCLUDE: \\(.*\\)" nil t) (whe
(let ((case-fold-search t)) (goto-char (point-min)) (while (re-search-forw
org-export-expand-include-keyword()
[...]
--8<---------------cut here---------------end--------------->8---
Note that the uml.org file referred to by the #+include exists. Also
note that the old exporter works.
I am not entirely sure what the semantics for included files in the new
exporter are. For instance, is an include statement /within/ a
non-exported headline meant to be processed?
Regardless, the fact that it fails to export is a bug, I guess.
Thanks,
eric
--
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.1.1 and Org release_7.9.2-516-g796fca
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: examplebug.org --]
[-- Type: text/orgmode, Size: 452 bytes --]
# -*- org-confirm-babel-evaluate: nil; -*-
#+TITLE: examplebug.org
#+AUTHOR: Eric S Fraga
#+EMAIL: e.fraga@ucl.ac.uk
#+DATE: 2012-01-09 Mon
#+EXPORT_EXCLUDE_TAGS: noexport
* introduction
This is some text that should be exported
* conclusions :noexport:
This is some text that will not be exported. It includes some text
from another file. The presence of this include causes the new
exporter to fail.
#+include: uml.org
next reply other threads:[~2012-10-28 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 10:42 Eric S Fraga [this message]
2012-10-28 11:29 ` [bug] [new-exporter] #+includes in non-exported regions do not work Myles English
2012-10-29 8:51 ` Eric S Fraga
2012-10-29 13:21 ` Nicolas Goaziou
2012-10-29 20:19 ` Eric S Fraga
2012-10-29 21:42 ` Sebastien Vauban
2012-10-29 22:00 ` 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=87mwz63mjx.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).