Re: Bug: exporter bug [8.3.1 (8.3.1-elpaplus <at> /home/dfeich/.emacs.d/elpa/org-plus-contrib-20150805/)]

[Ilya Yanok <ilya.yanok@gmail.com>]

Hi everybody,

Derek Feichtinger <dfeich <at> gmail.com> writes: 
> The current MELPA version (see version details below) seems to have
problems with
> the exporter. I reinstalled several times from older configurations to
> try and exlude local effects. I get the error with all exporters I tried
> 
> The file I am exporting is
> 
>
https://github.com/dfeich/org-babel-examples/blob/master/latex/latex-example.org
> 
> 
> Best regards
> Derek
> 
> Backtrace (long lines cut for this mail):
> 
> ################
> Debugger entered--Lisp error: (wrong-type-argument listp #("Derek
Feichtinger" 0 17 (:parent (#1))))
>   org-element-set-contents(#("Derek Feichtinger" 0 17 (:parent (#0)))) ...
>   ...
>   org-element-map((#("Derek Feichtinger" 0 17 (:parent #0))) plain-text ...
>   org-export--get-inbuffer-options([cl-struct-org-export-backend latex nil ...
>   org-export-get-environment([cl-struct-org-export-backend latex nil ...
>   org-export-as(latex nil nil nil (:output-file "./latex-example.tex"))
>   org-export-to-file(latex "./latex-example.tex" nil nil nil nil nil
#[(file) ...
>   org-latex-export-to-pdf(nil nil nil nil)
>   (org-open-file (org-latex-export-to-pdf nil s v b))
>   (if a (org-latex-export-to-pdf t s v b) (org-open-file
(org-latex-export-to-pdf nil s v b)))
>   (lambda (a s v b) (if a (org-latex-export-to-pdf t s v b) (org-open-file
(org-latex-export-to-pdf nil s v b))))(nil nil nil nil)
>   org-export-dispatch(nil)
>   call-interactively(org-export-dispatch nil nil)
>   command-execute(org-export-dispatch)
> #############

this is a pretty old report, but I would like to bring it back to life,
since I'm experiencing the same issue and I did some investigation.


I've found that in ox.el org-export--get-inbuffer-options function calls
org-element-map ... 'plain-text with a function that tries to use
org-element-set-element. But according to org-element.el, plaint-text
elements don't have a content and couldn't be set! So I believe this code is
buggy anyway. It's possible that this bug is not triggered in some (most)
configurations, because the code is not executed, but this doesn't make this
code correct anyway.

Unfortunately I'm not an expert in org-mode internals and don't have any
idea how to fix that. Looking forward for your help here.

Regards, Ilya.