Re: [O] DEADLINE: position in entry
On Wed, 09 Nov 2016 18:37:00 +0900,
Alan Tyree wrote:
>
> Is this the way it should be? The first DEADLINE: shows up both as a
> warning and on the due date in the agenda, but the second one does
> not. It only works for me if the DEADLINE: is the first line after the
> heading. Version 9, emacs 24
>
> *** test 1
> DEADLINE: <2016-11-19 Sat>
>
> *** test 2
>
> DEADLINE: <2016-11-19 Sat>
at release_9.0.1-47-gb062593 with the following org file, org-agenda
shows the closed entry. Is this also related?
Yes, org-lint complains about the 4th "scheduled" line saying:
"Misplaced planning info line", but isn't deadline planning info line?
is any of planning info line not allowed in the body?
>8 cut >8
* DONE org
DEADLINE: [2016-01-07 Thu 17:39]
SCHEDULED: <2015-09-29 Tue .+1w>
>8 cut >8
; /tmp/a.el
(add-to-list 'load-path "~/src/org-mode/lisp")
(setq org-agenda-files '("/tmp/a.org"))
>8 cut >8
$ emacs -Q -l /tmp/a.el -f 'org-agenda'
--
yashi
[O] ELPA vs 9.0.1 release (still issues)
I'm not enough of an ELPA guru to figure this out. I tried org-mode 9.0.1 using ELPA, found some issues I'll describe, and find that using the direct git version does not have those issues. All of this is with Emacs 24.5.2, GTK+ version 2.24.31. This is a fresh setup, no other packages installed, but my .emacs is from a working setup. My first test of a new version is a babel invocation of R with a large table sent as a variable to R: #+name: glucose_analysis #+begin_src R :file 1.png :results graphics :var data=glucose :width 1200 :height 600 library(ggplot2) ... Test results: 1) The ELPA install from org repository of 20161118 had numerous compile issues. The immediately relevant one is: Compiling file /home/hornrj/.emacs.d/elpa/org-20161118/org-element.el at Sun Nov 20 13:33:22 2016 In org-element--get-node-properties: org-element.el:938:25:Warning: reference to free variable `org-planning-line-re' In org-element--get-time-properties: org-element.el:953:45:Warning: reference to free variable `org-planning-line-re' In org-element--current-element: org-element.el:3850:26:Warning: reference to free variable `org-planning-line-re' org-element.el:3862:21:Warning: reference to free variable `org-clock-line-re' In end of data: org-element.el:6124:1:Warning: the following functions are not known to be defined: org-link-types, org-macro-extract-arguments The invocation of R failed with an error that org-link-types was not known. 2) I deleted all the .elc files in the ELPA directory The result was an incredibly slow invocation of R. It took 6 minutes to parse and prepare the table. (It's only about 2,000 line table.) Then it invoked R, generated the diagram, etc. So it passed the test but was incredibly slow. 3) I removed the ELPA installed directory, cloned the git repository, did a "make compile" which generated no errors, and linked from elpa to the lisp directory. The test ran in a few seconds. So there remains something wrong in the ELPA setup. R Horn rjh...@alum.mit.edu
[O] Citation syntax: now supported in Pandoc
Hi everyone, With Org 9.0 out, I thought it might be a good time to revisit the issue of citation syntax. Not much has happened with this recently, but I do have one bit of progress to report: About six months ago, Albert Krewinkel, who maintains the support for Org syntax in Pandoc [1], wrote to me about supporting the citation syntax we discussed previously, and that is partially implemented in the wip-cite branch. You can see examples of the syntax at [2]. Albert dove in, and was able to quickly add support for the syntax to Pandoc's Org reader. This support has been merged into released versions of Pandoc. Albert actually announced this a few months ago on Reddit [3], but it looks like he did not email this list. I finally got a chance to check out his work yesterday. I converted one citation-heavy chapter of my dissertation to use the new syntax, and tested out Pandoc's support, with a couple of different CSL stylesheets, including a note-based style. It works great. Thanks, Albert, for your hard work! There are some minor issues that probably need more discussion after real-world use (like whether/when a conjunction should be inserted automatically before the last reference in a multi-cite citation). But as far as I can tell, Albert has correctly implemented everything we actually discussed and agreed on. In short, Pandoc now has support for Org citation syntax, and that support is fully integrated with Pandoc's citation processing capabilities. So there is now at least one "real" (non-prototype) solution for processing Org citations via CSL, with output to HTML, LaTeX, ODT, .docx, and the other formats that Pandoc supports. This makes it a lot easier for people to test out the syntax in the real world, so I encourage you to do so, and report back on what you find! Best, Richard [1] http://pandoc.org/ [2] https://github.com/wyleyr/org-citeproc/blob/master/tests/testdoc.org [3] https://www.reddit.com/r/orgmode/comments/4tes4x/ann_pandoc_v1172_has_been_released_it_now/
[O] html export fails on new setup
I'm trying to set up a new MacBook Pro to run org-mode (among other
things. I'm trying to export a simple file to HTML, and getting an
error.
Here's the file:
#+begin_src org
#+STARTUP: showeverything logdone
#+options: num:nil toc:nil
#+author: Peter Davis
#+title: Test
html export test
#+end_src
The backtrace is attached, but the error is:
Debugger entered--Lisp error: (wrong-type-argument listp #("Test" 0 4
(:parent (#1
Any clues?
Thanks,
-pd
--
Peter Davis
www.techcurmudgeon.com
Debugger entered--Lisp error: (wrong-type-argument listp #("Test" 0 4 (:parent
(#1
org-element-set-contents(#("Test" 0 4 (:parent (#0
apply(org-element-set-contents #("Test" 0 4 (: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)"](#("Test" 0 4 (: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)"](#("Test" 0 4 (: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 propert
Re: [O] renumber/resort footnotes?
Stig Brautaset writes: > Hi Sharon, > > Sharon Kimble writes: > >> How can I renumber or resort my footnotes please? > > =C-u C-c C-x f= (=org-footnote-action=) offers an action to sort footnotes, in > the footnotes section. You can also re-number them throughout the document > from here. > Thanks for this Stig. I eventually went through the document and manually reordered them. Thanks Sharon. -- A taste of linux = http://www.sharons.org.uk TGmeds = http://www.tgmeds.org.uk Debian 8.4, fluxbox 1.3.7, emacs 25.1.1 signature.asc Description: PGP signature
Re: [O] Release 9.0 test failed: test-ob/indented-cached-org-bracket-link
Hello, "Charles C. Berry" writes: > OTOH, (expand-file-name "test.txt") resolves double-slashes and seems > like the right idiom in any case. Fixed. Thank you. Regards, -- Nicolas Goaziou
