Re: [bug] [new-exporter] #+includes in non-exported regions do not work

["Myles English" <mylesenglish@gmail.com>]

Hi Eric,

You have:

  #+include: uml.org

I think it should be:

  #+include: "uml.org"

I have haven't tried it though.

Myles


Eric S Fraga writes:

> 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