Re: [O] migrating to the snapshot api
Apologies for bumping this, I was wondering if anybody had any more thoughts on migrating this backend to the latest version of org-mode? Seems to be something changed that isn't in the migration notes... On 21 August 2017 at 19:21, Sam Halliday wrote: > 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
[O] migrating to the snapshot api
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
Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
By running this (cl-delete-if (lambda (el) (string-match-p "/usr/share/.*org" el)) load-path) I'm able to hide org and now the org-plus-contrib loads up, yay! Thanks for the hints. On 21 August 2017 at 01:40, Kaushal Modi wrote: > On Sun, Aug 20, 2017, 4:25 PM Nicolas Goaziou > wrote: >> >> >> > then I can try to investigate what could be causing the Emacs org >> > to load. I cannot see how that is possible since it is not even >> > available on the elisp path anymore. >> > >> > Is there a way to check which elisp files have been loaded? Then I can >> > grep for anything from the emacs org install instead of my local >> > install. >> >> `locate-library' may help. Also, `load-path' can give a clue. Try with >> a bare configuration, i.e., with just >> >> (require 'package) >> (package-initialize) >> >> It can be tricky to find out what is loading bundled Org too early. >> Enjoy the Frankenorg. > > > :) > > M-x list-load-path-shadows will also help. Pay attention to shadows on org > packages. > > -- > > Kaushal Modi
Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
On 20 August 2017 at 16:07, Nicolas Goaziou wrote: > Hello, > > Sam Halliday writes: > >> To ensure that the Emacs-installed org-mode is not interfering, I >> added this to my init >> >> (cl-delete-if >>(lambda (el) (string-match-p ".*org" el)) >>load-path) >> >> and I can confirm that emacs/org is not in my load-path. >> >> However, the backtrace still occurs. > > As I wrote, it is still a problem of mixed installation. Quoting the > manual > > Recent Emacs distributions include a packaging system which lets you > install Elisp libraries. You can install Org with ‘M-x package-install > RET org’. > > Important: you need to do this in a session where no ‘.org’ file has > been visited, i.e., where no Org built-in function have been loaded. > Otherwise autoload Org functions will mess up the installation. > > Then, to make sure your Org configuration is taken into account, > initialize the package system with ‘(package-initialize)’ in your > ‘.emacs’ before setting any Org option. If you want to use Org’s > package repository, check out the Org ELPA page > (http://orgmode.org/elpa.html). Yes, I followed this exactly and the problem still occurs. If you are confirming that org is definitely compatible with my .org file then I can try to investigate what could be causing the Emacs org to load. I cannot see how that is possible since it is not even available on the elisp path anymore. Is there a way to check which elisp files have been loaded? Then I can grep for anything from the emacs org install instead of my local install.
Re: [O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
Hi Nicholas, To ensure that the Emacs-installed org-mode is not interfering, I added this to my init (cl-delete-if (lambda (el) (string-match-p ".*org" el)) load-path) and I can confirm that emacs/org is not in my load-path. However, the backtrace still occurs. For a much larger file that causes additional problems with org-mode markdown export (e.g. problems with BEGIN_SRC blocks) is my book's manuscript: https://github.com/fommil/fp-scala-mortals/blob/master/manuscript/book.org I am able to successfully export this using the built-in org-mode. Although I'm using additional extensions of md as per https://github.com/fommil/dotfiles/blob/master/.emacs.d/lisp/ox-leanpub.el I'm restricting my experiments to stock org-md for now. Best regards, Sam On 19 August 2017 at 10:50, Nicolas Goaziou wrote: > Hello, > > Sam Halliday writes: > >> Regression in org-plus-contrib from http://orgmode.org/elpa/ vs version >> distributed with Emacs 25.2.1 >> >> Running >> >> M-x md-org-export-to-markdown >> >> on a simple org file such as the following >> >> == >> >> #+TITLE: Functional Programming in Scala for Mortals >> >> /Functional Programming in Scala for Mortals/ is a book aimed at Scala >> developers with an Object Oriented background who wish to learn the >> *Functional Programming* paradigm. >> == >> >> Causes the following backtrace: >> >> Debugger entered--Lisp error: (wrong-type-argument listp #("Functional >> Programming in Scala for Mortals" 0 43 (:parent (#1 > > This usually mean that you have a mixed installation. You should check > that the Org shipped with Emacs is not used. > > Regards, > > -- > Nicolas Goaziou
[O] Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
Regression in org-plus-contrib from http://orgmode.org/elpa/ vs version distributed with Emacs 25.2.1 Running M-x md-org-export-to-markdown on a simple org file such as the following == #+TITLE: Functional Programming in Scala for Mortals /Functional Programming in Scala for Mortals/ is a book aimed at Scala developers with an Object Oriented background who wish to learn the *Functional Programming* paradigm. == Causes the following backtrace: Debugger entered--Lisp error: (wrong-type-argument listp #("Functional Programming in Scala for Mortals" 0 43 (:parent (#1 org-element-set-contents(#("Functional Programming in Scala for Mortals" 0 43 (:parent (#0 apply(org-element-set-contents #("Functional Programming in Scala for Mortals" 0 43 (:parent (#0))) nil) #[257 "\211\305\306\307#\310\311\211:\204 \312\202\"\n@9\203!\nAA\202\"\n)\"\210\313\314 \211:\2043\312\202@\n@9\203?\nAA\202@\n)#\210\315\211 \n;\203V\316\317\n#\202\\\320\nA@\"*\211;\203n\321\n\312\f$\202z\nA\322\nA@\f#\240\210\n+\210 AA@\240\210@\240*\207" [new old element property value replace-regexp-in-string "\n" " " mapc #[(blob) "\305 \211;\203 \306\f\307\n$\202 \fA\310\fA@\n#\240\210\f+\207" [blob old value property element :parent org-add-props nil plist-put] 6] nil apply org-element-set-contents :parent get-text-property 0 plist-get org-add-props plist-put] 7 "\n\n(fn S)"](#("Functional Programming in Scala for Mortals" 0 43 (:parent (#0 #[257 "\211\211:\204 \211;\205 \311\262\202 \211@9\205 \211@\262?\206\251\301\203-\312\301\313\">\206\251\211\2049\314\310\242\"\202\251\211\315=\203]\314\310\242\211:\204N\316\262\202Y\211@9\203Y\211AA\262\"\202\251\211\304>\203~\300!\211\203}\302\203v\317\320\"\210\202}\307\307\242B\240\210\210\306\321=\203\271;\204\271\211\236A\211\203\270\211@\310\242\211;\203\247\322\323#\266\202\202\257\312A@\"\266\202!\210A\266\202\202\216\210\303\203Q\306\321=\203Q\324!\325=\203Q\211\203P\211@\211@A\211;\203\347\322\323#\266\202\202\357\312A@\"\266\202\211\203G\235\2030\235\203!\326!\211\203\211@\310\242A!\210\310\242@!\210A\266\202\202\210\202G\310\242A!\210\310\242@!\210\202G\235\203B\314\310\242\326!\"\210\202G\310\242!\210\266A\266\202\202\315\210\211\305>\206\251\211:\204c\316\262\202n\211@9\203n\211AA\262?\206\251\306\327=\203\200\211>?\206\251\306\330=\203\216\324!\331=\206\251\314\310\242\211:\204\235\316\262\202\250\211@9\203\250\211AA\262\"\207" [#[257 "\211\305\306\307#\310\311\211:\204 \312\202\"\n@9\203!\nAA\202\"\n)\"\210\313\314 \211:\2043\312\202@\n@9\203?\nAA\202@\n)#\210\315\211 \n;\203V\316\317\n#\202\\\320\nA@\"*\211;\203n\321\n\312\f$\202z\nA\322\nA@\f#\240\210\n+\210 AA@\240\210@\240*\207" [new old element property value replace-regexp-in-string "\n" " " mapc #[(blob) "\305 \211;\203 \306\f\307\n$\202 \fA\310\fA@\n#\240\210\f+\207" [blob old value property element :parent org-add-props nil plist-put] 6] nil apply org-element-set-contents :parent get-text-property 0 plist-get org-add-props plist-put] 7 "\n\n(fn S)"] nil nil nil (plain-text) nil objects (nil) (#0) plain-text plist-get :ignore-list mapc org-data nil throw :--map-first-match objects get-text-property 0 org-element-class element reverse greater-elements elements object org-element-secondary-value-alist org-element--parsed-properties-alist org-element-dual-keywords org-element-multiple-keywords org-element-greater-elements] 11 "\n\n(fn --DATA)"](#("Functional Programming in Scala for Mortals" 0 43 (:parent (#0 mapc(#[257 "\211\211:\204 \211;\205 \311\262\202 \211@9\205 \211@\262?\206\251\301\203-\312\301\313\">\206\251\211\2049\314\310\242\"\202\251\211\315=\203]\314\310\242\211:\204N\316\262\202Y\211@9\203Y\211AA\262\"\202\251\211\304>\203~\300!\211\203}\302\203v\317\320\"\210\202}\307\307\242B\240\210\210\306\321=\203\271;\204\271\211\236A\211\203\270\211@\310\242\211;\203\247\322\323#\266\202\202\257\312A@\"\266\202!\210A\266\202\202\216\210\303\203Q\306\321=\203Q\324!\325=\203Q\211\203P\211@\211@A\211;\203\347\322\323#\266\202\202\357\312A@\"\266\202\211\203G\235\2030\235\203!\326!\211\203\211@\310\242A!\210\310\242@!\210A\266\202\202\210\202G\310\242A!\210\310\242@!\210\202G\235\203B\314\310\242\326!\"\210\202G\310\242!\210\266A\266\202\202\315\210\211\305>\206\251\211:\204c\316\262\202n\211@9\203n\211AA\262?\206\251\306\327=\203\200\211>?\206\251\306\330=\203\216\324!\331=\206\251\314\310\242\211:\204\235\316\262\202\250\211@9\203\250\211AA\262\"\207" [#[257 "\211\305\306\307#\310\311\211:\204 \312\202\"\n@9\203!\nAA\202\"\n)\"\210\313\314 \211:\2043\312\202@\n@9\203?\nAA\202@\n)#\210\315\211 \n;\203V\316\317\n#\202\\\320\nA@\"*\211;\203n\321\n\312\f$\202z\nA\322\nA@\f#\240\210\n+\210 AA@\240\210@\240*\207" [new old element property value repl
[O] ox-md and ox-leanpub
Hi all, I am starting to write a CC BY-SA 4.0 textbook and I want to be able to write it in org-mode and publish it on leanpub. I have hit some problems. I install org-mode on emacs 25.1 from http://orgmode.org/elpa/ like this (use-package org :ensure org-plus-contrib :defer t) (require 'ox-md) If I try to export the draft of my book https://raw.githubusercontent.com/fommil/fp-scala-mortals/master/book.org using C-c C-e and select m m (Markdown), I get this error: Debugger entered--Lisp error: (wrong-type-argument listp #("2017" 0 4 (:parent (#1 org-element-set-contents(#("2017" 0 4 (:parent (#0 apply(org-element-set-contents #("2017" 0 4 (:parent (#0))) nil) If I revert back to the version of ox-md that comes with Emacs 25.1, the file is exported ok. However, further to this. If I (require 'ox-leanpub) and C-c C-e using the default version of org-mode, then the option to export to Leanpub does not appear. Could somebody who knows how to write exporters please have a look over https://raw.githubusercontent.com/juanre/ox-leanpub/master/ox-leanpub.el to see if they can spot any obvious problems? If I install ox-leanpub with the latest org-plus-contrib then the :export-block line must be removed or it will fail to load. -- Best regards, Sam signature.asc Description: PGP signature
[O] fails to start on 32 bit
Dear org-mode authors, I discovered an error on startup on a 32 bit Windows build. The line in org-footnote.el (format "fn:%x" (random #x1)) is too large and this fails with an overflow. Please consider using a number that is 32bit compatible, I'm sure there are plenty of integers in the 32bit range for footnote IDs :-) -- Best regards, Sam signature.asc Description: PGP signature