[O] org-copy-subtree: Invalid function: org-preserve-local-variables
Using org version 9.2 and emacs version 26.1 I received the error in the subject line when trying to move or archive subtrees. It seems to me that this is related to the (eval-and-compile (require 'org-macs)) line in org.el as replacing it with (require 'org-macs) solved that problem. Can someone tell me whether this is actually related to something else that I may have set up faulty or whether there is a more correct fix. Thanks,
Re: [O] batch failure of first org-num test
Sorry, I just now spotted an earlier message from Kaushal that reports the same test failure: https://lists.gnu.org/archive/html/emacs-orgmode/2019-01/msg00112.html
[O] batch failure of first org-num test
Hello,
When I run the tests on master in batch (specifically ‘make test’),
test-org-num/format-function fails (backtrace at end of message). That
test doesn't fail if I run it interactively.
Looking at test-org-num.el, I see that the first test,
test-org-num/face, is commented with the explanation “FIXME: this test
fails in batch mode”. So it seems that commenting out that test just
pushes the failure down the line. And indeed if I comment out
test-org-num/format-function, the next test fails.
I don’t have an understanding of the underlying issue, but if I add
‘(require 'org-num)’ to test-org-num.el, all tests pass for me with
‘make test’.
--8<---cut here---start->8---
Test test-org-num/format-function backtrace:
signal(ert-test-failed (((should (equal '("foo" "foo") (org-test-wit
ert-fail(((should (equal '("foo" "foo") (org-test-with-temp-text "*
(if (unwind-protect (setq value-8786 (apply fn-8784 args-8785)) (set
(let (form-description-8788) (if (unwind-protect (setq value-8786 (a
(let ((value-8786 'ert-form-evaluation-aborted-8787)) (let (form-des
(let* ((fn-8784 (function equal)) (args-8785 (condition-case err (le
(closure (t) nil (let* ((fn-8784 (function equal)) (args-8785 (condi
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name test-org-num/format-function :documen
ert-run-or-rerun-test(#s(ert--stats :selector "\\(org\\|ob\\)" :test
ert-run-tests("\\(org\\|ob\\)" #f(compiled-function (event-type
ert-run-tests-batch("\\(org\\|ob\\)")
ert-run-tests-batch-and-exit("\\(org\\|ob\\)")
(let ((org-id-track-globally t) (org-test-selector (if org-test-sele
org-test-run-batch-tests("\\(org\\|ob\\)")
eval((org-test-run-batch-tests org-test-select-re))
command-line-1(("--eval" "(setq vc-handled-backends nil org-startup-
command-line()
normal-top-level()
Test test-org-num/format-function condition:
(ert-test-failed
((should
(equal '...
(org-test-with-temp-text "* H1
** H2" ... ...)))
:form
(equal
("foo" "foo")
(#("1.1 " 0 4 ...)
#("1 " 0 2 ...)))
:value nil :explanation
(list-elt 0
(arrays-of-different-length 3 4 "foo"
#("1.1 " 0 4 ...)
first-mismatch-at 0
--8<---cut here---end--->8---
Re: [O] horizontal rules in table confuse org-table-iterate
Hi Hendrik, Everything above the first hline is considered a table heading, and is therefore not included in calculations. This is explained in the docs: https://orgmode.org/manual/Updating-the-table.html On Mon, Jan 07, 2019 at 04:23:01PM +0100, Hendrik Tews wrote: > org-table-iterate does not update tables for me. In the following > table: > > | 1 | 1 | > | 2 | 2 | > |---+---| > | 3 | 4 | > #+TBLFM: $2=$1+1::@3$1=vsum(@1..@2) > > M-x org-table-iterate does not update the table, although I was > expecting a 2 in cell @1$2. If I delete the horizontal rule, the > table is updated. Am I doing something wrong?
[O] horizontal rules in table confuse org-table-iterate
Hi, with Emacs 26.1 and org-mode version 9.2 (release_9.2-148-g7d638d @ ~/src/org-mode/lisp/), org-table-iterate does not update tables for me. In the following table: | 1 | 1 | | 2 | 2 | |---+---| | 3 | 4 | #+TBLFM: $2=$1+1::@3$1=vsum(@1..@2) M-x org-table-iterate does not update the table, although I was expecting a 2 in cell @1$2. If I delete the horizontal rule, the table is updated. Am I doing something wrong? Thanks, Hendrik
Re: [O] please read: bug when marking tasks done
hi nicolas, Nicolas Goaziou writes: > Hello, > > cesar mena writes: > >> hello everyone, >> >> in the maint branch, marking a repeatable task as DONE causes the >> "Rescheduled from" dates to be lost in the :LOGBOOK:. >> >> in the below diff all of the from dates are rewritten with the new >> scheduled date: >> >> - SCHEDULED: <2018-12-04 Tue .+1m> >> + SCHEDULED: <2019-02-05 Tue .+1m> >> :PROPERTIES: >> - :LAST_REPEAT: [2018-08-08 Wed 07:40] >> + :LAST_REPEAT: [2019-01-05 Sat 18:47] >> :END: >> :LOGBOOK: >> - - Rescheduled from "[2018-11-28 Wed .+1m]" on [2018-11-28 Wed 08:35] >> - - Rescheduled from "[2018-11-25 Sun .+1m]" on [2018-11-25 Sun 09:17] >> - - Rescheduled from "[2018-11-20 Tue .+1m]" on [2018-11-22 Thu 10:03] >> - - Rescheduled from "[2018-11-13 Tue .+1m]" on [2018-11-17 Sat 09:48] >> - - Rescheduled from "[2018-11-06 Tue .+1m]" on [2018-11-08 Thu 07:02] >> - - Rescheduled from "[2018-10-28 Sun .+1m]" on [2018-10-30 Tue 16:22] >> - - Rescheduled from "[2018-10-25 Thu .+1m]" on [2018-10-25 Thu 07:34] >> - - Rescheduled from "[2018-10-19 Fri .+1m]" on [2018-10-19 Fri 07:48] >> - - Rescheduled from "[2018-10-16 Tue .+1m]" on [2018-10-16 Tue 16:21] >> - - Rescheduled from "[2018-10-11 Thu .+1m]" on [2018-10-14 Sun 10:31] >> - - Rescheduled from "[2018-10-07 Sun .+1m]" on [2018-10-08 Mon 08:48] >> - - Rescheduled from "[2018-09-27 Thu .+1m]" on [2018-09-29 Sat 18:50] >> - - Rescheduled from "[2018-09-20 Thu .+1m]" on [2018-09-20 Thu 09:50] >> - - Rescheduled from "[2018-09-08 Sat .+1m]" on [2018-09-14 Fri 07:10] >> + - State "DONE" from "TODO" [2019-01-05 Sat 18:47] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-28 Wed 08:35] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-25 Sun 09:17] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-22 Thu 10:03] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-17 Sat 09:48] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-08 Thu 07:02] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-30 Tue 16:22] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-25 Thu 07:34] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-19 Fri 07:48] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-16 Tue 16:21] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-14 Sun 10:31] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-08 Mon 08:48] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-29 Sat 18:50] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-20 Thu 09:50] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-14 Fri 07:10] >> >> bisect says it was introduced in >> af81211fdc01b64449179bcdb77fb1c8ecb3fb94. > > Which is a bugfix… as per the documentation for "org-auto-repeat-maybe" only the base date of repeating deadline/scheduled time stamps should change. AFAICT the patch changes every occurrence of an inactive repeating timestamp that is not a comment. > I think a solution would be to remove the repeater from timestamps > inserted upon logging a state change or a re-scheduling. but that is useful and correct information. it lets me know the state of the scheduled timestamp at the time i rescheduled; you are proposing to change this to avoid a re-computation for data that i am sure we agree should be treated as immutable. note that the from dates in the "Rescheduled" line is also in quotes indicating that it is textual information. no longer in play. changing such dates is akin to changing dates in a comment. what do you think? best, -cm
Re: [O] please read: bug when marking tasks done
Nicolas Goaziou writes: > Hello, > > cesar mena writes: > >> hello everyone, >> >> in the maint branch, marking a repeatable task as DONE causes the >> "Rescheduled from" dates to be lost in the :LOGBOOK:. >> >> in the below diff all of the from dates are rewritten with the new >> scheduled date: >> >> - SCHEDULED: <2018-12-04 Tue .+1m> >> + SCHEDULED: <2019-02-05 Tue .+1m> >> :PROPERTIES: >> - :LAST_REPEAT: [2018-08-08 Wed 07:40] >> + :LAST_REPEAT: [2019-01-05 Sat 18:47] >> :END: >> :LOGBOOK: >> - - Rescheduled from "[2018-11-28 Wed .+1m]" on [2018-11-28 Wed 08:35] >> - - Rescheduled from "[2018-11-25 Sun .+1m]" on [2018-11-25 Sun 09:17] >> - - Rescheduled from "[2018-11-20 Tue .+1m]" on [2018-11-22 Thu 10:03] >> - - Rescheduled from "[2018-11-13 Tue .+1m]" on [2018-11-17 Sat 09:48] >> - - Rescheduled from "[2018-11-06 Tue .+1m]" on [2018-11-08 Thu 07:02] >> - - Rescheduled from "[2018-10-28 Sun .+1m]" on [2018-10-30 Tue 16:22] >> - - Rescheduled from "[2018-10-25 Thu .+1m]" on [2018-10-25 Thu 07:34] >> - - Rescheduled from "[2018-10-19 Fri .+1m]" on [2018-10-19 Fri 07:48] >> - - Rescheduled from "[2018-10-16 Tue .+1m]" on [2018-10-16 Tue 16:21] >> - - Rescheduled from "[2018-10-11 Thu .+1m]" on [2018-10-14 Sun 10:31] >> - - Rescheduled from "[2018-10-07 Sun .+1m]" on [2018-10-08 Mon 08:48] >> - - Rescheduled from "[2018-09-27 Thu .+1m]" on [2018-09-29 Sat 18:50] >> - - Rescheduled from "[2018-09-20 Thu .+1m]" on [2018-09-20 Thu 09:50] >> - - Rescheduled from "[2018-09-08 Sat .+1m]" on [2018-09-14 Fri 07:10] >> + - State "DONE" from "TODO" [2019-01-05 Sat 18:47] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-28 Wed 08:35] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-25 Sun 09:17] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-22 Thu 10:03] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-17 Sat 09:48] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-11-08 Thu 07:02] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-30 Tue 16:22] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-25 Thu 07:34] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-19 Fri 07:48] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-16 Tue 16:21] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-14 Sun 10:31] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-10-08 Mon 08:48] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-29 Sat 18:50] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-20 Thu 09:50] >> + - Rescheduled from "[2019-02-05 Tue .+1m]" on [2018-09-14 Fri 07:10] >> >> bisect says it was introduced in >> af81211fdc01b64449179bcdb77fb1c8ecb3fb94. > > Which is a bugfix… > > I think a solution would be to remove the repeater from timestamps > inserted upon logging a state change or a re-scheduling. > > However, you would have to fix your old documents manually. > > Regards, Hi Nicholas, I think this commit is a problem: af81211fd (Also obey to repeaters in inactive time stamps, 2018-11-10) At the beginning of the year I close my repeating tasks with lots of logging and clocking entries and create a new one as follows: 1) Clone repeating task to new task for next year 2) Unscheduled old task which writes the scheduled repeater to the log as above 3) Mark old task DONE Step 3 fails. It moves the repeater in the log message from the old scheduled task makes the task TODO again. Example: * TODO Sample repeating task 2018 SCHEDULED: <2019-01-07 Mon ++1w> :LOGBOOK: - Note taken on [2019-01-07 Mon 09:44] \\ Log note 2 - Note taken on [2019-01-07 Mon 09:44] \\ Log note 1 :END: [2019-01-07 Mon 09:44] Now clone the task with C-c C-x c 1 RET RET * TODO Sample repeating task 2018 SCHEDULED: <2019-01-07 Mon ++1w> :LOGBOOK: - Note taken on [2019-01-07 Mon 09:44] \\ Log note 2 - Note taken on [2019-01-07 Mon 09:44] \\ Log note 1 :END: [2019-01-07 Mon 09:44] * TODO Sample repeating task 2018 SCHEDULED: <2019-01-07 Mon ++1w> :LOGBOOK: - Note taken on [2019-01-07 Mon 09:44] \\ Log note 2 - Note taken on [2019-01-07 Mon 09:44] \\ Log note 1 :END: [2019-01-07 Mon 09:44] Rename the second task to 2019 and unschedule the first task: * TODO Sample repeating task 2018
Re: [O] funny remote time/duration values
On Mon, 7 Jan 2019 11:29:15 +0100, Robert Klein wrote: > > Hi, > > when using values (time/duration) from a remote table I sometimes get > funny values: > > > #+name: teta > | 4:50 | > > > | 2:25 | > #+TBLFM: @1$1=remote(teta,@1$1) > > > When I set e.g. 7:50 in “teta” the same value shows up in the second > table (after C-u C-c C-c). > > For 1:00 in “teta” I get #ERROR in the second table. same in all cases > with a 0 in front (04:50, 07:50, 01:00). > > > Org-version is 9.2 > > Any ideas? It seems they are treated as (calc) fractions and simplified. -- Michał Politowski
[O] Failing org-num-mode test
Hello Nicolas,
While recently working on few Org tag fixes in org.el, I was running make
test, and saw 1 test related to the recently added org-num-mode fail.
The failure can be quickly recreated with:
make test BTEST_RE=test-org-num
=
Test test-org-num/format-function condition:
(ert-test-failed
((should
(equal '...
(org-test-with-temp-text "* H1
** H2" ... ...)))
:form
(equal
("foo" "foo")
(#("1.1 " 0 4 ...)
#("1 " 0 2 ...)))
:value nil :explanation
(list-elt 0
(arrays-of-different-length 3 4 "foo"
#("1.1 " 0 4 ...)
first-mismatch-at 0
FAILED 1/4 test-org-num/format-function (0.002472 sec)
passed 2/4 test-org-num/max-level (0.000511 sec)
passed 3/4 test-org-num/skip-numbering (0.003965 sec)
passed 4/4 test-org-num/update (0.038399 sec)
Ran 4 tests, 3 results as expected, 1 unexpected (2019-01-07 08:32:35-0500,
0.184330 sec)
1 unexpected results:
FAILED test-org-num/format-function
=
Can you confirm?
--
Kaushal Modi
Re: [O] funny remote time/duration values
On Mon, 7 Jan 2019 11:29:15 +0100, Robert Klein wrote: > > Hi, > > when using values (time/duration) from a remote table I sometimes get > funny values: > > > #+name: teta > | 4:50 | > > > | 2:25 | > #+TBLFM: @1$1=remote(teta,@1$1) > > > When I set e.g. 7:50 in “teta” the same value shows up in the second > table (after C-u C-c C-c). > > For 1:00 in “teta” I get #ERROR in the second table. same in all cases > with a 0 in front (04:50, 07:50, 01:00). > > > Org-version is 9.2 > > Any ideas? It seems you need the 'T' flag here, as described in "Duration and time values" in the org manual: #+TBLFM: @1$1=remote(teta,@1$1);T -- Michał Politowski
Re: [O] funny remote time/duration values
On Monday, 7 Jan 2019 at 10:58, Robert Klein wrote: > Hi, > > when using values (time/duration) from a remote table I sometimes get > funny values: > > #+name: teta > | 4:50 | > > | 2:25 | > #+TBLFM: @1$1=remote(teta,@1$1) Note that x:y in Emacs calc (which is what org uses for the spreadsheet elements of tables) is a ratio so 4:50 *is* the same as 2:25. If you have times, you'll need to use different notation (@,',", I believe). -- Eric S Fraga via Emacs 27.0.50, Org release_9.1.14-1035-gfeb442
[O] funny remote time/duration values
Hi, when using values (time/duration) from a remote table I sometimes get funny values: #+name: teta | 4:50 | | 2:25 | #+TBLFM: @1$1=remote(teta,@1$1) When I set e.g. 7:50 in “teta” the same value shows up in the second table (after C-u C-c C-c). For 1:00 in “teta” I get #ERROR in the second table. same in all cases with a 0 in front (04:50, 07:50, 01:00). Org-version is 9.2 Any ideas? Thanks and best regards Robert -- Robert Klein UNIX Operations Max Planck-Institut für Polymerforschung Anschrift: Ackermannweg 10, 55128 Mainz
[O] funny remote time/duration values
Hi, when using values (time/duration) from a remote table I sometimes get funny values: #+name: teta | 4:50 | | 2:25 | #+TBLFM: @1$1=remote(teta,@1$1) When I set e.g. 7:50 in “teta” the same value shows up in the second table (after C-u C-c C-c). For 1:00 in “teta” I get #ERROR in the second table. same in all cases with a 0 in front (04:50, 07:50, 01:00). Org-version is 9.2 Any ideas? Thanks and best regards Robert
[O] org-feed-parse-atom-feed doesn't handle empty value
Hello,
I think there is a problem in org-feed-update in that it doesn't handle
an entry containing an element with no value, like this:
For example, adding an entry in org-feed-alist for an atom feed that
fails like this is:
("Artanis"
"https://gitlab.com/NalaGinrut/artanis/tags?format=atom;
"~/feeds.org" "Artanis"
:parse-entry org-feed-parse-atom-entry
:parse-feed org-feed-parse-atom-feed
:template "* TODO %title\n")
and calling org-feed-update results in a backtrace:
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
string-match("&\\(?:#\\(x\\)?\\([0-9a-fA-F]+\\)\\|\\([[:word:]:_][-0-9.[:word:]:_·̀-ͯ‿-⁀]*\\)\\);"
nil)
xml-substitute-special(nil)
(plist-put entry :description (xml-substitute-special (car (xml-node-children
content
(setq entry (plist-put entry :description (xml-substitute-special (car
(xml-node-children content)
(cond ((string= type "text") (setq entry (plist-put entry :description
(xml-substitute-special (car (xml-node-children content))
((string= type "html") (setq entry (plist-put entry :description
(xml-substitute-special (car (xml-node-children content))
((string= type "xhtml") (setq entry (plist-put entry :description
(prin1-to-string (xml-node-children content) (t (setq entry
(plist-put entry :description (format-message "Unknown `%s' content."
type)
(progn (cond ((string= type "text") (setq entry (plist-put entry
:description (xml-substitute-special (car (xml-node-children
content)) ((string= type "html") (setq entry (plist-put entry
:description (xml-substitute-special (car (xml-node-children
content)) ((string= type "xhtml") (setq entry (plist-put entry
:description (prin1-to-string (xml-node-children content) (t (setq
entry (plist-put entry :description (format-message "Unknown `%s'
content." type))
(if content (progn (cond ((string= type "text") (setq entry (plist-put
entry :description (xml-substitute-special (car (xml-node-children
content)) ((string= type "html") (setq entry (plist-put entry
:description (xml-substitute-special (car (xml-node-children
content)) ((string= type "xhtml") (setq entry (plist-put entry
:description (prin1-to-string (xml-node-children content) (t (setq
entry (plist-put entry :description (format-message "Unknown `%s'
content." type)))
(let* ((content (car (xml-get-children xml 'content))) (type
(xml-get-attribute-or-nil content 'type))) (if content (progn (cond
((string= type "text") (setq entry (plist-put entry :description
(xml-substitute-special (car (xml-node-children content))
((string= type "html") (setq entry (plist-put entry :description
(xml-substitute-special (car (xml-node-children content))
((string= type "xhtml") (setq entry (plist-put entry :description
(prin1-to-string (xml-node-children content) (t (setq entry
(plist-put entry :description (format-message "Unknown `%s' content."
type
(let ((xml (car (read-from-string (plist-get entry
:item-full-text) (setq entry (plist-put entry :link
(xml-get-attribute (car (xml-get-children xml 'link)) 'href))) (setq
entry (plist-put entry :title (xml-substitute-special (car
(xml-node-children (car (xml-get-children xml 'title))) (let*
((content (car (xml-get-children xml 'content))) (type
(xml-get-attribute-or-nil content 'type))) (if content (progn (cond
((string= type "text") (setq entry (plist-put entry :description
(xml-substitute-special (car (xml-node-children content))
((string= type "html") (setq entry (plist-put entry :description
(xml-substitute-special (car (xml-node-children content))
((string= type "xhtml") (setq entry (plist-put entry :description
(prin1-to-string (xml-node-children content) (t (setq entry
(plist-put entry :description (format-message "Unknown `%s' content."
type entry)
org-feed-parse-atom-entry((:guid
"https://gitlab.com/NalaGinrut/artanis/tags/v0.0.1; :item-full-text
"(entry nil \"\n \" (id nil
\"https://gitlab.com/NalaGinrut/artanis/tags/v0.0.1\;) \"\n \" (link
((href . \"https://gitlab.com/NalaGinrut/artanis/tags/v0.0.1\;))) \"\n
\" (title nil \"v0.0.1\") \"\n \" (summary nil \"first release\") \"\n
\" (content ((type . \"html\"))) \"\n \" (media:thumbnail ((width
. \"40\") (height . \"40\") (url
.
\"https://secure.gravatar.com/avatar/9a606d9c4e90d963463107046aa61e70?s=80=identicon\;)))
\"\n \" (author nil \"\n \" (name nil \"Nala Ginrut\") \"\n \" (email
nil \"nalagin...@gmail.com\") \"\n \") \"\n\")" :handled nil :link
"https://gitlab.com/NalaGinrut/artanis/tags/v0.0.1; :title "v0.0.1"))
mapcar(org-feed-parse-atom-entry ((:guid
"https://gitlab.com/NalaGinrut/artanis/tags/v0.0.1; :item-full-text
"(entry nil \"\n \" (id nil
\"https://gitlab.com/NalaGinrut/artanis/tags/v0.0.1\;) \"\n \" (link
((href .
Re: [O] Org mode repeated dates to do spaced learning
On 2019-01-06, at 18:17, Andrea Giugliano wrote: > Hi there, > > That was a very helpful suggestion. At the bottom of the mail I attached Glad to have helped! Best, -- Marcin Borkowski http://mbork.pl
