From: Sam Halliday <sam.halliday@gmail.com>
To: emacs-org list <Emacs-orgmode@gnu.org>
Subject: migrating to the snapshot api
Date: Mon, 21 Aug 2017 19:21:10 +0100 [thread overview]
Message-ID: <CALR_T9A5a54AtogR1VnURNF5nwH5XTT+20xPWBjCUaUWQum3mQ@mail.gmail.com> (raw)
Hi all,
I maintain a fork of an org-mode backend for a markdown based
publishing format
https://github.com/fommil/dotfiles/blob/master/.emacs.d/lisp/ox-leanpub.el
Which works great for the org-mode that ships with emacs 25.2.
However, when I use the latest org-mode from the snapshots on even the
most simple of files, e.g. the one line
==========
Wibble wibble I'm a fish
==========
I get a stacktrace like this (huge amount of data elided)
==========
Debugger entered--Lisp error: (wrong-type-argument sequencep :back-end)
mapc(#[
mapc(#[
org-element-map(
org-export--footnote-reference-map(
org-export-collect-footnote-definitions(
org-leanpub-inner-template(
org-export-as(leanpub nil nil nil nil)
org-export-to-buffer(leanpub "*Org LEANPUB Export*" nil nil nil nil
nil (lambda nil (text-mode)))
org-leanpub-export-as-markdown()
funcall-interactively(org-leanpub-export-as-markdown)
call-interactively(org-leanpub-export-as-markdown record nil)
command-execute(org-leanpub-export-as-markdown record)
execute-extended-command(nil "org-leanpub-export-as-markdown" nil)
funcall-interactively(execute-extended-command nil
"org-leanpub-export-as-markdown" nil)
call-interactively(execute-extended-command nil nil)
command-execute(execute-extended-command)
==========
From reading http://orgmode.org/Changes.html#org1e55804 I can see that
I am supposed to remove the :export-block, which I have done locally.
Can anybody see what else I need to change to be compatible with the
latest version?
Best regards,
Sam
next reply other threads:[~2017-08-21 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 18:21 Sam Halliday [this message]
2017-08-25 8:19 ` migrating to the snapshot api Sam Halliday
2017-08-25 9:43 ` 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=CALR_T9A5a54AtogR1VnURNF5nwH5XTT+20xPWBjCUaUWQum3mQ@mail.gmail.com \
--to=sam.halliday@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).