* strange errors with org-element-cache-reset and jit-lock-function void-variable org-element-citation-prefix-re
@ 2022-09-20 19:17 Daniel Ortmann
2022-09-21 8:37 ` Ihor Radchenko
0 siblings, 1 reply; 6+ messages in thread
From: Daniel Ortmann @ 2022-09-20 19:17 UTC (permalink / raw)
To: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
Hmmm ...
While trying to investigate one bug I have run into another odd one:
* emacs version: GNU Emacs 29.0.50 (build 23, x86_64-pc-linux-gnu,
GTK+ Version 3.22.30, cairo version 1.15.12) of 2022-09-20
* org version: Org mode version 9.5.5 (release_9.5.5-804-gf1a197 @
/home/dortmann/src/git-org-mode/lisp/)
These two lines are in my *Messages* buffer:
File mode specification error: (void-function org-element-cache-reset)
Error during redisplay: (jit-lock-function 1) signaled (void-variable
org-element-citation-prefix-re)
I ran this:
dortmann@ddo-linux:.emacs.d$ emacs -Q --debug-init asdf.el
... and then ran eval-buffer.
Where asdf.el has this content:
(add-to-list 'load-path "/home/dortmann/src/git-org-mode/lisp")
(require 'org)
(setq org-capture-templates
`(("c" "Item to current clocked task" checkitem
(clock)
"%i%?" :prepend t :empty-lines 1)))
Then I loaded asdf.org which has this:
* TODO start clock on this test item
The result is the failure message above. :-/
[-- Attachment #2: Type: text/html, Size: 1674 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: strange errors with org-element-cache-reset and jit-lock-function void-variable org-element-citation-prefix-re
2022-09-20 19:17 strange errors with org-element-cache-reset and jit-lock-function void-variable org-element-citation-prefix-re Daniel Ortmann
@ 2022-09-21 8:37 ` Ihor Radchenko
2022-09-22 18:05 ` [External] : " Daniel Ortmann
0 siblings, 1 reply; 6+ messages in thread
From: Ihor Radchenko @ 2022-09-21 8:37 UTC (permalink / raw)
To: Daniel Ortmann; +Cc: emacs-orgmode
Daniel Ortmann <daniel.ortmann@oracle.com> writes:
> These two lines are in my *Messages* buffer:
> File mode specification error: (void-function org-element-cache-reset)
> Error during redisplay: (jit-lock-function 1) signaled (void-variable
> org-element-citation-prefix-re)
Confirmed.
I know how to "fix" this (can just add require 'org-element into
`org-mode'), but I do not fully understand what is going on on Emacs
side.
Let's see what Emacs devs say.
See https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57972
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [External] : Re: strange errors with org-element-cache-reset and jit-lock-function void-variable org-element-citation-prefix-re
2022-09-21 8:37 ` Ihor Radchenko
@ 2022-09-22 18:05 ` Daniel Ortmann
2022-09-23 2:07 ` Ihor Radchenko
0 siblings, 1 reply; 6+ messages in thread
From: Daniel Ortmann @ 2022-09-22 18:05 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: emacs-orgmode
Was Eli Z's observation the key? Of code not autoloading when
eval-buffer is running?
On 9/21/22 03:37, Ihor Radchenko wrote:
> Daniel Ortmann <daniel.ortmann@oracle.com> writes:
>
>> These two lines are in my *Messages* buffer:
>> File mode specification error: (void-function org-element-cache-reset)
>> Error during redisplay: (jit-lock-function 1) signaled (void-variable
>> org-element-citation-prefix-re)
> Confirmed.
> I know how to "fix" this (can just add require 'org-element into
> `org-mode'), but I do not fully understand what is going on on Emacs
> side.
>
> Let's see what Emacs devs say.
> See https://urldefense.com/v3/__https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57972__;!!ACWV5N9M2RV99hQ!I8yBQdVtvdB9WZzgR3JRtDsvGImyGOhqd8fkT_pXuN02wF5lk8ftp-3v1HiF-T3Rn-eyiQIr2BhjbxqK_bo$
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [External] : Re: strange errors with org-element-cache-reset and jit-lock-function void-variable org-element-citation-prefix-re
2022-09-22 18:05 ` [External] : " Daniel Ortmann
@ 2022-09-23 2:07 ` Ihor Radchenko
2022-09-25 2:44 ` Bastien Guerry
0 siblings, 1 reply; 6+ messages in thread
From: Ihor Radchenko @ 2022-09-23 2:07 UTC (permalink / raw)
To: Daniel Ortmann, Bastien; +Cc: emacs-orgmode
Daniel Ortmann <daniel.ortmann@oracle.com> writes:
> Was Eli Z's observation the key? Of code not autoloading when
> eval-buffer is running?
Yes, it is.
Bastien,
In f36b19eef, you introduced the following code into org.el:
(or (eq this-command 'eval-buffer)
(condition-case nil
(load (concat (file-name-directory load-file-name)
"org-loaddefs.el")
nil t t t)
(error
(message "WARNING: No org-loaddefs.el file could be found from where org.el is loaded.")
(sit-for 3)
(message "You need to run \"make\" or \"make autoloads\" from Org lisp directory")
(sit-for 3))))
The commit message explains why we display warning, but it is unclear
why (eq this-command ...) check is performed.
This check is causing the issue herein. Also, see
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57972
I am leaning towards removing `this-command' check, unless there are
important reasons to keep it.
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2022-09-25 6:04 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-09-20 19:17 strange errors with org-element-cache-reset and jit-lock-function void-variable org-element-citation-prefix-re Daniel Ortmann
2022-09-21 8:37 ` Ihor Radchenko
2022-09-22 18:05 ` [External] : " Daniel Ortmann
2022-09-23 2:07 ` Ihor Radchenko
2022-09-25 2:44 ` Bastien Guerry
2022-09-25 6:03 ` Ihor Radchenko
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).