[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#22469: closed (org-mode export fail)

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#22469: closed (org-mode export fail)
Date: Fri, 01 Dec 2017 21:44:01 +0000

Your message dated Fri, 01 Dec 2017 22:43:11 +0100
with message-id <address@hidden>
and subject line Re: bug#22469: org-mode export fail
has caused the debbugs.gnu.org bug report #22469,
regarding org-mode export fail
to be marked as done.

(If you believe you have received this mail in error, please contact

22469: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22469
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: org-mode export fail Date: Tue, 26 Jan 2016 14:14:37 +0000 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
I am seeing this error from org-mode when trying to export to HTML. The
main org file has an include line like so:

#+INCLUDE: "sisyphus.org" :lines "28-"

The error occurs on a clean emacs -q run from head of Emacs-25.

I don't quite understand where the error is coming from, given that this
simple export has nothing to do with agenda files.

Org-files are attached.



Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  org-map-entries(#[nil "\300\301 !\207" [org-reduced-level org-current-level] 
"28-" 0 1)
  org-export-as(html nil nil nil (:output-file "./sisyphus-doc.html"))
  org-export-to-file(html "./sisyphus-doc.html" nil nil nil nil nil)
  org-html-export-to-html(nil nil nil nil)
  funcall-interactively(org-export-dispatch nil)
  call-interactively(org-export-dispatch nil nil)

Attachment: sisyphus-doc.org
Description: Text Data

Attachment: sisyphus.org
Description: Text Data

--- End Message ---
--- Begin Message --- Subject: Re: bug#22469: org-mode export fail Date: Fri, 01 Dec 2017 22:43:11 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
Kyle Meyer <address@hidden> writes:

> address@hidden (Phillip Lord) writes:
>> Kyle Meyer <address@hidden> writes:
> [...]
>>> This should be fixed on the Org side as of 44c8cd7 (2015-08-10):
> [...]
>> Okay. What's the best way to get this fix onto the release branch?
> I'm not sure, but I just asked a related question in bug#22399:
>     http://thread.gmane.org/gmane.emacs.bugs/111992

Closing this bug since the issue is solved and the fix landed in Emacs
release branch.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]