* Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
@ 2017-08-19 9:45 Sam Halliday
2017-08-19 9:50 ` Nicolas Goaziou
0 siblings, 1 reply; 17+ messages in thread
From: Sam Halliday @ 2017-08-19 9:45 UTC (permalink / raw)
To: emacs-orgmode
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#\x19\310\311\b\211:\204\0\312\202\"\n@9\203!\nAA\202\"\n)\"\210\313\314 \b\211:\2043\312\202@\n@9\203?\nAA\202@\n)#\210\b\315\211 ^[\n;\203V\316\317\v\n#\202\\\320\nA@\v\"*^[\211;\203n\321\n\312\v\f$\202z\nA\322\nA@\v\f#\240\210\n+\210 A\bA@\240\210 \b@\240*\207" [new old element property value replace-regexp-in-string "\n" " " mapc #[(blob) "\b\305 ^[\211;\203\0\306\f\307\v\n$\202 \fA\310\fA@\v\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\0\211;\205\0\311\262\202\0\211@9\205\0\211@\262\x01?\206\251\301\203-\x01\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\x01;\204\271\211\x1a\236A\211\203\270\211@\310\242\x05\211;\203\247\322\323\x03#\266\202\202\257\312A@\"\266\202!\210A\266\202\202\216\210\303\203Q\306\321=\203Q\324!\325=\203Q\x0e\211\203P\211@\211@A\211;\203\347\322\323\x03#\266\202\202\357\312A@\"\266\202\211\203G\x01\x1c\235\2030\x01\x1d\235\203!\326!\211\203\x01\211@\310\242A!\210\310\242@!\210A\266\202\202\x01\210\202G\310\242A!\210\310\242@!\210\202G\x01\x1d\235\203B\314\310\242\326!\"\210\202G\310\242!\210\266\x01A\266\202\202\315\210\211\305>\206\251\x01\211:\204c\316\262\202n\211@9\203n\211AA\262?\206\251\306\327=\203\200\211\x1e>?\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#\x19\310\311\b\211:\204\0\312\202\"\n@9\203!\nAA\202\"\n)\"\210\313\314 \b\211:\2043\312\202@\n@9\203?\nAA\202@\n)#\210\b\315\211 ^[\n;\203V\316\317\v\n#\202\\\320\nA@\v\"*^[\211;\203n\321\n\312\v\f$\202z\nA\322\nA@\v\f#\240\210\n+\210 A\bA@\240\210 \b@\240*\207" [new old element property value replace-regexp-in-string "\n" " " mapc #[(blob) "\b\305 ^[\211;\203\0\306\f\307\v\n$\202 \fA\310\fA@\v\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\0\211;\205\0\311\262\202\0\211@9\205\0\211@\262\x01?\206\251\301\203-\x01\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\x01;\204\271\211\x1a\236A\211\203\270\211@\310\242\x05\211;\203\247\322\323\x03#\266\202\202\257\312A@\"\266\202!\210A\266\202\202\216\210\303\203Q\306\321=\203Q\324!\325=\203Q\x0e\211\203P\211@\211@A\211;\203\347\322\323\x03#\266\202\202\357\312A@\"\266\202\211\203G\x01\x1c\235\2030\x01\x1d\235\203!\326!\211\203\x01\211@\310\242A!\210\310\242@!\210A\266\202\202\x01\210\202G\310\242A!\210\310\242@!\210\202G\x01\x1d\235\203B\314\310\242\326!\"\210\202G\310\242!\210\266\x01A\266\202\202\315\210\211\305>\206\251\x01\211:\204c\316\262\202n\211@9\203n\211AA\262?\206\251\306\327=\203\200\211\x1e>?\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#\x19\310\311\b\211:\204\0\312\202\"\n@9\203!\nAA\202\"\n)\"\210\313\314 \b\211:\2043\312\202@\n@9\203?\nAA\202@\n)#\210\b\315\211 ^[\n;\203V\316\317\v\n#\202\\\320\nA@\v\"*^[\211;\203n\321\n\312\v\f$\202z\nA\322\nA@\v\f#\240\210\n+\210 A\bA@\240\210 \b@\240*\207" [new old element property value replace-regexp-in-string "\n" " " mapc #[(blob) "\b\305 ^[\211;\203\0\306\f\307\v\n$\202 \fA\310\fA@\v\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))))
#[257 "\211\211:\204\0\211;\205\0\311\262\202\0\211@9\205\0\211@\262\x01?\206\251\301\203-\x01\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\x01;\204\271\211\x1a\236A\211\203\270\211@\310\242\x05\211;\203\247\322\323\x03#\266\202\202\257\312A@\"\266\202!\210A\266\202\202\216\210\303\203Q\306\321=\203Q\324!\325=\203Q\x0e\211\203P\211@\211@A\211;\203\347\322\323\x03#\266\202\202\357\312A@\"\266\202\211\203G\x01\x1c\235\2030\x01\x1d\235\203!\326!\211\203\x01\211@\310\242A!\210\310\242@!\210A\266\202\202\x01\210\202G\310\242A!\210\310\242@!\210\202G\x01\x1d\235\203B\314\310\242\326!\"\210\202G\310\242!\210\266\x01A\266\202\202\315\210\211\305>\206\251\x01\211:\204c\316\262\202n\211@9\203n\211AA\262?\206\251\306\327=\203\200\211\x1e>?\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#\x19\310\311\b\211:\204\0\312\202\"\n@9\203!\nAA\202\"\n)\"\210\313\314 \b\211:\2043\312\202@\n@9\203?\nAA\202@\n)#\210\b\315\211 ^[\n;\203V\316\317\v\n#\202\\\320\nA@\v\"*^[\211;\203n\321\n\312\v\f$\202z\nA\322\nA@\v\f#\240\210\n+\210 A\bA@\240\210 \b@\240*\207" [new old element property value replace-regexp-in-string "\n" " " mapc #[(blob) "\b\305 ^[\211;\203\0\306\f\307\v\n$\202 \fA\310\fA@\v\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))))
org-element-map((#("Functional Programming in Scala for Mortals" 0 43 (:parent #0))) plain-text #[257 "\211\305\306\307#\x19\310\311\b\211:\204\0\312\202\"\n@9\203!\nAA\202\"\n)\"\210\313\314 \b\211:\2043\312\202@\n@9\203?\nAA\202@\n)#\210\b\315\211 ^[\n;\203V\316\317\v\n#\202\\\320\nA@\v\"*^[\211;\203n\321\n\312\v\f$\202z\nA\322\nA@\v\f#\240\210\n+\210 A\bA@\240\210 \b@\240*\207" [new old element property value replace-regexp-in-string "\n" " " mapc #[(blob) "\b\305 ^[\211;\203\0\306\f\307\v\n$\202 \fA\310\fA@\v\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)"])
org-export--get-inbuffer-options([cl-struct-org-export-backend md html ((bold . org-md-bold) (code . org-md-verbatim) (example-block . org-md-example-block) (export-block . org-md-export-block) (fixed-width . org-md-example-block) (headline . org-md-headline) (horizontal-rule . org-md-horizontal-rule) (inline-src-block . org-md-verbatim) (inner-template . org-md-inner-template) (italic . org-md-italic) (item . org-md-item) (keyword . org-md-keyword) (line-break . org-md-line-break) (link . org-md-link) (node-property . org-md-node-property) (paragraph . org-md-paragraph) (plain-list . org-md-plain-list) (plain-text . org-md-plain-text) (property-drawer . org-md-property-drawer) (quote-block . org-md-quote-block) (section . org-md-section) (src-block . org-md-example-block) (template . org-md-template) (verbatim . org-md-verbatim)) ((:md-footnote-format nil nil org-md-footnote-format) (:md-footnotes-section nil nil org-md-footnotes-section) (:md-headline-style nil nil org-md-headline-style)) ((:filter-parse-tree . org-md-separate-elements)) nil (109 "Export to Markdown" ((77 "To temporary buffer" (lambda (a s v b) (org-md-export-as-markdown a s v))) (109 "To file" (lambda (a s v b) (org-md-export-to-markdown a s v))) (111 "To file and open" (lambda (a s v b) (if a (org-md-export-to-markdown t s v) (org-open-file (org-md-export-to-markdown nil s v)))))))])
org-export-get-environment([cl-struct-org-export-backend md html ((bold . org-md-bold) (code . org-md-verbatim) (example-block . org-md-example-block) (export-block . org-md-export-block) (fixed-width . org-md-example-block) (headline . org-md-headline) (horizontal-rule . org-md-horizontal-rule) (inline-src-block . org-md-verbatim) (inner-template . org-md-inner-template) (italic . org-md-italic) (item . org-md-item) (keyword . org-md-keyword) (line-break . org-md-line-break) (link . org-md-link) (node-property . org-md-node-property) (paragraph . org-md-paragraph) (plain-list . org-md-plain-list) (plain-text . org-md-plain-text) (property-drawer . org-md-property-drawer) (quote-block . org-md-quote-block) (section . org-md-section) (src-block . org-md-example-block) (template . org-md-template) (verbatim . org-md-verbatim)) ((:md-footnote-format nil nil org-md-footnote-format) (:md-footnotes-section nil nil org-md-footnotes-section) (:md-headline-style nil nil org-md-headline-style)) ((:filter-parse-tree . org-md-separate-elements)) nil (109 "Export to Markdown" ((77 "To temporary buffer" (lambda (a s v b) (org-md-export-as-markdown a s v))) (109 "To file" (lambda (a s v b) (org-md-export-to-markdown a s v))) (111 "To file and open" (lambda (a s v b) (if a (org-md-export-to-markdown t s v) (org-open-file (org-md-export-to-markdown nil s v)))))))] nil (:output-file "./README.md"))
org-export-as(md nil nil nil (:output-file "./README.md"))
org-export-to-file(md "./README.md" nil nil nil)
org-md-export-to-markdown()
funcall-interactively(org-md-export-to-markdown)
call-interactively(org-md-export-to-markdown record nil)
command-execute(org-md-export-to-markdown record)
execute-extended-command(nil "org-md-export-to-markdown" nil)
funcall-interactively(execute-extended-command nil "org-md-export-to-markdown" nil)
call-interactively(execute-extended-command nil nil)
command-execute(execute-extended-command)
------------------------------------------------------------------------
Emacs : GNU Emacs 25.2.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.22.16)
of 2017-07-16
Package: Org mode version 9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)
current state:
==============
(setq
org-tab-first-hook '(org-babel-hide-result-toggle-maybe
org-babel-header-arg-expand)
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-occur-hook '(org-first-headline-recenter)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-html-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
org-latex-format-inlinetask-function 'org-latex-format-inlinetask-default-function
org-confirm-shell-link-function 'yes-or-no-p
org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
org-latex-format-headline-function 'org-latex-format-headline-default-function
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-latex-format-drawer-function #[514 "\207" [] 3 "\n\n(fn _ CONTENTS)"]
org-odt-format-headline-function 'org-odt-format-headline-default-function
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-babel-pre-tangle-hook '(save-buffer)
org-mode-hook '(#[0 "\300\301\302\303\304$\207"
[add-hook change-major-mode-hook org-show-block-all append local]
5]
#[0 "\300\301\302\303\304$\207"
[add-hook change-major-mode-hook org-babel-show-result-all
append local]
5]
org-babel-result-hide-spec org-babel-hide-all-hashes
writing-mode-hooks
(closure (t) nil (yas-minor-mode t) (company-mode t)
(visual-line-mode t)
(local-set-key (kbd "s-c") (quote picture-mode))
(org-babel-do-load-languages (quote org-babel-load-languages)
(quote ((ditaa . t) (dot . t))))
)
org-eldoc-load)
org-archive-hook '(org-attach-archive-delete-maybe)
org-ascii-format-drawer-function #[771 "\207" [] 4 "\n\n(fn NAME CONTENTS WIDTH)"]
org-odt-format-inlinetask-function 'org-odt-format-inlinetask-default-function
org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
org-cycle-show-empty-lines
org-optimize-window-after-visibility-change)
org-confirm-elisp-link-function 'yes-or-no-p
org-metadown-hook '(org-babel-pop-to-session-maybe)
org-odt-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
org-ditaa-jar-path "/home/fommil/.ditaa.jar"
org-html-format-headline-function 'org-html-format-headline-default-function
org-link-parameters '(("id" :follow org-id-open)
("rmail" :follow org-rmail-open :store org-rmail-store-link)
("mhe" :follow org-mhe-open :store org-mhe-store-link)
("irc" :follow org-irc-visit :store org-irc-store-link)
("info" :follow org-info-open :export org-info-export :store
org-info-store-link)
("gnus" :follow org-gnus-open :store org-gnus-store-link)
("docview" :follow org-docview-open :export
org-docview-export :store org-docview-store-link)
("bibtex" :follow org-bibtex-open :store
org-bibtex-store-link)
("bbdb" :follow org-bbdb-open :export org-bbdb-export
:complete org-bbdb-complete-link :store org-bbdb-store-link)
("w3m" :store org-w3m-store-link) ("file+sys")
("file+emacs") ("doi" :follow org--open-doi-link)
("elisp" :follow org--open-elisp-link)
("file" :complete org-file-complete-link)
("ftp" :follow
(lambda (path) (browse-url (concat "ftp:" path))))
("help" :follow org--open-help-link)
("http" :follow
(lambda (path) (browse-url (concat "http:" path))))
("https" :follow
(lambda (path) (browse-url (concat "https:" path))))
("mailto" :follow
(lambda (path) (browse-url (concat "mailto:" path))))
("message" :follow
(lambda (path) (browse-url (concat "message:" path))))
("news" :follow
(lambda (path) (browse-url (concat "news:" path))))
("shell" :follow org--open-shell-link))
org-babel-load-languages '((ditaa . t) (dot . t))
org-html-format-inlinetask-function 'org-html-format-inlinetask-default-function
org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
org-confirm-babel-evaluate nil
org-export-headline-levels 5
)
--
Best regards,
Sam
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-08-19 9:45 Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)] Sam Halliday
@ 2017-08-19 9:50 ` Nicolas Goaziou
2017-08-20 14:47 ` Sam Halliday
0 siblings, 1 reply; 17+ messages in thread
From: Nicolas Goaziou @ 2017-08-19 9:50 UTC (permalink / raw)
To: Sam Halliday; +Cc: emacs-orgmode
Hello,
Sam Halliday <sam.halliday@gmail.com> 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
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-08-19 9:50 ` Nicolas Goaziou
@ 2017-08-20 14:47 ` Sam Halliday
2017-08-20 15:07 ` Nicolas Goaziou
0 siblings, 1 reply; 17+ messages in thread
From: Sam Halliday @ 2017-08-20 14:47 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: emacs-orgmode
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 <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> Sam Halliday <sam.halliday@gmail.com> 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
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-08-20 14:47 ` Sam Halliday
@ 2017-08-20 15:07 ` Nicolas Goaziou
2017-08-20 18:10 ` Sam Halliday
0 siblings, 1 reply; 17+ messages in thread
From: Nicolas Goaziou @ 2017-08-20 15:07 UTC (permalink / raw)
To: Sam Halliday; +Cc: emacs-orgmode
Hello,
Sam Halliday <sam.halliday@gmail.com> 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).
Some users install Org launching a new Emacs session without any
configuration file.
> 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
Could you point out what are the problems? I have no issue exporting the
document above with latest Org, but I may have missed some wrong bits in
the output. I have no Scala mode installed.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-08-20 15:07 ` Nicolas Goaziou
@ 2017-08-20 18:10 ` Sam Halliday
2017-08-20 20:23 ` Nicolas Goaziou
0 siblings, 1 reply; 17+ messages in thread
From: Sam Halliday @ 2017-08-20 18:10 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: emacs-orgmode
On 20 August 2017 at 16:07, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> Sam Halliday <sam.halliday@gmail.com> 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.
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-08-20 18:10 ` Sam Halliday
@ 2017-08-20 20:23 ` Nicolas Goaziou
2017-08-21 0:40 ` Kaushal Modi
0 siblings, 1 reply; 17+ messages in thread
From: Nicolas Goaziou @ 2017-08-20 20:23 UTC (permalink / raw)
To: Sam Halliday; +Cc: emacs-orgmode
Sam Halliday <sam.halliday@gmail.com> writes:
> If you are confirming that org is definitely compatible with my .org
> file
It is, although I didn't check the details of the output. It didn't
error in the process anyway.
> 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.
Regards,
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-08-20 20:23 ` Nicolas Goaziou
@ 2017-08-21 0:40 ` Kaushal Modi
2017-08-21 17:32 ` Sam Halliday
2017-09-02 2:48 ` Adam Porter
0 siblings, 2 replies; 17+ messages in thread
From: Kaushal Modi @ 2017-08-21 0:40 UTC (permalink / raw)
To: Nicolas Goaziou, Sam Halliday; +Cc: emacs-org list
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
On Sun, Aug 20, 2017, 4:25 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
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
[-- Attachment #2: Type: text/html, Size: 1406 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-08-21 0:40 ` Kaushal Modi
@ 2017-08-21 17:32 ` Sam Halliday
2017-09-02 2:48 ` Adam Porter
1 sibling, 0 replies; 17+ messages in thread
From: Sam Halliday @ 2017-08-21 17:32 UTC (permalink / raw)
To: Kaushal Modi; +Cc: emacs-org list, Nicolas Goaziou
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 <kaushal.modi@gmail.com> wrote:
> On Sun, Aug 20, 2017, 4:25 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
> 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
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-08-21 0:40 ` Kaushal Modi
2017-08-21 17:32 ` Sam Halliday
@ 2017-09-02 2:48 ` Adam Porter
2017-09-02 3:01 ` Kaushal Modi
1 sibling, 1 reply; 17+ messages in thread
From: Adam Porter @ 2017-09-02 2:48 UTC (permalink / raw)
To: emacs-orgmode
Kaushal Modi <kaushal.modi@gmail.com> writes:
> M-x list-load-path-shadows will also help. Pay attention to shadows on org packages.
Wow, I did not know about that command. I have a bit of cleaning-up to
do. :)
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-09-02 2:48 ` Adam Porter
@ 2017-09-02 3:01 ` Kaushal Modi
2017-09-02 3:30 ` Adam Porter
2017-09-04 6:03 ` Loris Bennett
0 siblings, 2 replies; 17+ messages in thread
From: Kaushal Modi @ 2017-09-02 3:01 UTC (permalink / raw)
To: Adam Porter, emacs-org list
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On Fri, Sep 1, 2017, 10:49 PM Adam Porter <adam@alphapapa.net> wrote:
> Kaushal Modi <kaushal.modi@gmail.com> writes:
>
> > M-x list-load-path-shadows will also help. Pay attention to shadows on
> org packages.
>
> Wow, I did not know about that command. I have a bit of cleaning-up to
> do. :)
>
That's what I did when I found the shadows too :)
Here's how I make sure no mixed installations happen among Emacs-built-in,
Elpa and git Org versions:
https://scripter.co/building-org-development-version/
In addition to load-path, I also handle Info-path so that the correct Org
manual gets loaded.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1400 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-09-02 3:01 ` Kaushal Modi
@ 2017-09-02 3:30 ` Adam Porter
2017-09-04 6:03 ` Loris Bennett
1 sibling, 0 replies; 17+ messages in thread
From: Adam Porter @ 2017-09-02 3:30 UTC (permalink / raw)
To: emacs-orgmode
Wow, thanks, that is comprehensive. :)
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-09-02 3:01 ` Kaushal Modi
2017-09-02 3:30 ` Adam Porter
@ 2017-09-04 6:03 ` Loris Bennett
2017-09-04 22:43 ` Adam Porter
1 sibling, 1 reply; 17+ messages in thread
From: Loris Bennett @ 2017-09-04 6:03 UTC (permalink / raw)
To: emacs-orgmode
Kaushal Modi <kaushal.modi@gmail.com> writes:
> On Fri, Sep 1, 2017, 10:49 PM Adam Porter <adam@alphapapa.net> wrote:
>
> Kaushal Modi <kaushal.modi@gmail.com> writes:
>
> > M-x list-load-path-shadows will also help. Pay attention to shadows on org packages.
>
> Wow, I did not know about that command. I have a bit of cleaning-up to
> do. :)
>
> That's what I did when I found the shadows too :)
>
> Here's how I make sure no mixed installations happen among
> Emacs-built-in, Elpa and git Org versions:
> https://scripter.co/building-org-development-version/
>
> In addition to load-path, I also handle Info-path so that the correct
> Org manual gets loaded.
I didn't know about this function either. Is it correct that the org
parts of 'org-plus-contrib' shadow the whole of 'org', e.g.
...
/home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org hides /usr/share/emacs/25.1/lisp/org/org
/home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org-install hides /usr/share/emacs/25.1/lisp/org/org-install
/home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-mscgen hides /usr/share/emacs/25.1/lisp/org/ob-mscgen
/home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org-archive hides /usr/share/emacs/25.1/lisp/org/org-archive
/home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-tangle hides /usr/share/emacs/25.1/lisp/org/ob-tangle
...
plus hundreds of similar shadowings?
Cheers,
Loris
--
Dr. Loris Bennett (Mr.)
ZEDAT, Freie Universität Berlin Email loris.bennett@fu-berlin.de
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-09-04 6:03 ` Loris Bennett
@ 2017-09-04 22:43 ` Adam Porter
2017-09-05 6:21 ` Loris Bennett
0 siblings, 1 reply; 17+ messages in thread
From: Adam Porter @ 2017-09-04 22:43 UTC (permalink / raw)
To: emacs-orgmode
"Loris Bennett" <loris.bennett@fu-berlin.de> writes:
> I didn't know about this function either. Is it correct that the org
> parts of 'org-plus-contrib' shadow the whole of 'org', e.g.
>
> ...
> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org hides /usr/share/emacs/25.1/lisp/org/org
> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org-install hides /usr/share/emacs/25.1/lisp/org/org-install
> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-mscgen hides /usr/share/emacs/25.1/lisp/org/ob-mscgen
> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org-archive hides /usr/share/emacs/25.1/lisp/org/org-archive
> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-tangle hides /usr/share/emacs/25.1/lisp/org/ob-tangle
> ...
>
> plus hundreds of similar shadowings?
That's shadowing the Org files distributed with Emacs; you want that. :)
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-09-04 22:43 ` Adam Porter
@ 2017-09-05 6:21 ` Loris Bennett
2017-09-05 7:41 ` Tim Cross
0 siblings, 1 reply; 17+ messages in thread
From: Loris Bennett @ 2017-09-05 6:21 UTC (permalink / raw)
To: emacs-orgmode
Adam Porter <adam@alphapapa.net> writes:
> "Loris Bennett" <loris.bennett@fu-berlin.de> writes:
>
>> I didn't know about this function either. Is it correct that the org
>> parts of 'org-plus-contrib' shadow the whole of 'org', e.g.
>>
>> ...
>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org hides /usr/share/emacs/25.1/lisp/org/org
>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org-install hides /usr/share/emacs/25.1/lisp/org/org-install
>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-mscgen hides /usr/share/emacs/25.1/lisp/org/ob-mscgen
>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org-archive hides /usr/share/emacs/25.1/lisp/org/org-archive
>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-tangle hides /usr/share/emacs/25.1/lisp/org/ob-tangle
>> ...
>>
>> plus hundreds of similar shadowings?
>
> That's shadowing the Org files distributed with Emacs; you want that. :)
D'oh, I copied the wrong bits. This was what I was wondering about:
...
/home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ox-md hides /home/loris/.emacs.d/elpa/org-20170828/ox-md
/home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-lilypond hides /home/loris/.emacs.d/elpa/org-20170828/ob-lilypond
/home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-ruby hides /home/loris/.emacs.d/elpa/org-20170828/ob-ruby
/home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-js hides /home/loris/.emacs.d/elpa/org-20170828/ob-js
/home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org-crypt hides /home/loris/.emacs.d/elpa/org-20170828/org-crypt
...
M-x list-packages shows 'org-plus-contrib' as installed and 'org' as a
dependency required by
ox-twiki-20170803.1339, org-sticky-header-20170422.2135, org-dotemacs-20151119.1022
So I guess the above packages should allow 'org-plus-contrib' as an
alternative requirement to 'org', but currently require only 'org', so I
end up with both installed.
Cheers,
Loris
--
Dr. Loris Bennett (Mr.)
ZEDAT, Freie Universität Berlin Email loris.bennett@fu-berlin.de
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-09-05 6:21 ` Loris Bennett
@ 2017-09-05 7:41 ` Tim Cross
2017-09-05 8:24 ` Loris Bennett
0 siblings, 1 reply; 17+ messages in thread
From: Tim Cross @ 2017-09-05 7:41 UTC (permalink / raw)
To: Loris Bennett; +Cc: emacs-orgmode
This is an artefact of having the two packages. The package system does
not support alternatives. I have posted a few times regarding this. I
don't think it does any harm, but many people will find they have both
org-plus-contrib as well as org installed. The main draw back is that
updates can take longer due to downloading org twice.
I and others have asked a few times why the packages are structured in
this way, but nobody seems able to provide the rationale. Personally, I
think we should just have an org package and an org-contrib package
which depends on the org package.
Tim
Loris Bennett writes:
> Adam Porter <adam@alphapapa.net> writes:
>
>> "Loris Bennett" <loris.bennett@fu-berlin.de> writes:
>>
>>> I didn't know about this function either. Is it correct that the org
>>> parts of 'org-plus-contrib' shadow the whole of 'org', e.g.
>>>
>>> ...
>>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org hides /usr/share/emacs/25.1/lisp/org/org
>>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org-install hides /usr/share/emacs/25.1/lisp/org/org-install
>>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-mscgen hides /usr/share/emacs/25.1/lisp/org/ob-mscgen
>>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org-archive hides /usr/share/emacs/25.1/lisp/org/org-archive
>>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-tangle hides /usr/share/emacs/25.1/lisp/org/ob-tangle
>>> ...
>>>
>>> plus hundreds of similar shadowings?
>>
>> That's shadowing the Org files distributed with Emacs; you want that. :)
>
> D'oh, I copied the wrong bits. This was what I was wondering about:
>
> ...
> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ox-md hides /home/loris/.emacs.d/elpa/org-20170828/ox-md
> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-lilypond hides /home/loris/.emacs.d/elpa/org-20170828/ob-lilypond
> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-ruby hides /home/loris/.emacs.d/elpa/org-20170828/ob-ruby
> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-js hides /home/loris/.emacs.d/elpa/org-20170828/ob-js
> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org-crypt hides /home/loris/.emacs.d/elpa/org-20170828/org-crypt
> ...
>
> M-x list-packages shows 'org-plus-contrib' as installed and 'org' as a
> dependency required by
>
> ox-twiki-20170803.1339, org-sticky-header-20170422.2135, org-dotemacs-20151119.1022
>
> So I guess the above packages should allow 'org-plus-contrib' as an
> alternative requirement to 'org', but currently require only 'org', so I
> end up with both installed.
>
> Cheers,
>
> Loris
--
Tim Cross
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-09-05 7:41 ` Tim Cross
@ 2017-09-05 8:24 ` Loris Bennett
2017-09-08 10:13 ` Adam Porter
0 siblings, 1 reply; 17+ messages in thread
From: Loris Bennett @ 2017-09-05 8:24 UTC (permalink / raw)
To: emacs-orgmode
Tim Cross <theophilusx@gmail.com> writes:
> Loris Bennett writes:
>
>> Adam Porter <adam@alphapapa.net> writes:
>>
>>> "Loris Bennett" <loris.bennett@fu-berlin.de> writes:
>>>
>>>> I didn't know about this function either. Is it correct that the org
>>>> parts of 'org-plus-contrib' shadow the whole of 'org', e.g.
>>>>
>>>> ...
>>>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org hides /usr/share/emacs/25.1/lisp/org/org
>>>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org-install hides /usr/share/emacs/25.1/lisp/org/org-install
>>>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-mscgen hides /usr/share/emacs/25.1/lisp/org/ob-mscgen
>>>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org-archive hides /usr/share/emacs/25.1/lisp/org/org-archive
>>>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-tangle hides /usr/share/emacs/25.1/lisp/org/ob-tangle
>>>> ...
>>>>
>>>> plus hundreds of similar shadowings?
>>>
>>> That's shadowing the Org files distributed with Emacs; you want that. :)
>>
>> D'oh, I copied the wrong bits. This was what I was wondering about:
>>
>> ...
>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ox-md hides /home/loris/.emacs.d/elpa/org-20170828/ox-md
>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-lilypond hides /home/loris/.emacs.d/elpa/org-20170828/ob-lilypond
>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-ruby hides /home/loris/.emacs.d/elpa/org-20170828/ob-ruby
>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/ob-js hides /home/loris/.emacs.d/elpa/org-20170828/ob-js
>> /home/loris/.emacs.d/elpa/org-plus-contrib-20170828/org-crypt hides /home/loris/.emacs.d/elpa/org-20170828/org-crypt
>> ...
>>
>> M-x list-packages shows 'org-plus-contrib' as installed and 'org' as a
>> dependency required by
>>
>> ox-twiki-20170803.1339, org-sticky-header-20170422.2135, org-dotemacs-20151119.1022
>>
>> So I guess the above packages should allow 'org-plus-contrib' as an
>> alternative requirement to 'org', but currently require only 'org', so I
>> end up with both installed.
>>
>> Cheers,
>>
>> Loris
>
> This is an artefact of having the two packages. The package system does
> not support alternatives. I have posted a few times regarding this. I
> don't think it does any harm, but many people will find they have both
> org-plus-contrib as well as org installed. The main draw back is that
> updates can take longer due to downloading org twice.
>
> I and others have asked a few times why the packages are structured in
> this way, but nobody seems able to provide the rationale. Personally, I
> think we should just have an org package and an org-contrib package
> which depends on the org package.
>
> Tim
>
So is there a specific reason why there is no 'org-contrib' package
without 'org'?
Cheers,
Loris
--
Dr. Loris Bennett (Mr.)
ZEDAT, Freie Universität Berlin Email loris.bennett@fu-berlin.de
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)]
2017-09-05 8:24 ` Loris Bennett
@ 2017-09-08 10:13 ` Adam Porter
0 siblings, 0 replies; 17+ messages in thread
From: Adam Porter @ 2017-09-08 10:13 UTC (permalink / raw)
To: emacs-orgmode
"Loris Bennett" <loris.bennett@fu-berlin.de> writes:
>> I and others have asked a few times why the packages are structured in
>> this way, but nobody seems able to provide the rationale. Personally, I
>> think we should just have an org package and an org-contrib package
>> which depends on the org package.
>>
>> Tim
>>
>
> So is there a specific reason why there is no 'org-contrib' package
> without 'org'?
Yes, that would seem to make more sense.
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2017-09-08 10:15 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-08-19 9:45 Bug: markdown export errors on headers [9.0.9 (9.0.9-82-gb862c2-elpaplus @ /home/fommil/.emacs.d/elpa/org-plus-contrib-20170814/)] Sam Halliday
2017-08-19 9:50 ` Nicolas Goaziou
2017-08-20 14:47 ` Sam Halliday
2017-08-20 15:07 ` Nicolas Goaziou
2017-08-20 18:10 ` Sam Halliday
2017-08-20 20:23 ` Nicolas Goaziou
2017-08-21 0:40 ` Kaushal Modi
2017-08-21 17:32 ` Sam Halliday
2017-09-02 2:48 ` Adam Porter
2017-09-02 3:01 ` Kaushal Modi
2017-09-02 3:30 ` Adam Porter
2017-09-04 6:03 ` Loris Bennett
2017-09-04 22:43 ` Adam Porter
2017-09-05 6:21 ` Loris Bennett
2017-09-05 7:41 ` Tim Cross
2017-09-05 8:24 ` Loris Bennett
2017-09-08 10:13 ` Adam Porter
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).