timer errors

[emacsomancer]

I seem to be getting org-node-related timer errors:

Error running timer: (cl-no-applicable-method #[(sortstr key) ((if (fboundp 'org-node-fakeroam-daily-create) (org-node-fakeroam-daily-create sortstr key t) (error "Not installed: org-node-fakeroam"))) nil] comp--spill-lap-function #[(sortstr key) ((if (fboundp 'org-node-fakeroam-daily-create) (org-node-fakeroam-daily-create sortstr key t) (error "Not installed: org-node-fakeroam"))) nil])
Error running timer: (cl-no-applicable-method #[(node) ((let ((time (cdr (assoc "CREATION_TIME" (org-node-get-props node))))) (when (and time (not (string-blank-p time))) (cons time (org-node-get-id node))))) nil] comp--spill-lap-function #[(node) ((let ((time (cdr (assoc "CREATION_TIME" (org-node-get-props node))))) (when (and time (not (string-blank-p time))) (cons time (org-node-get-id node))))) nil])
Error running timer: (cl-no-applicable-method #[(sortstr key) ((org-node-create sortstr (org-id-new) key)) nil] comp--spill-lap-function #[(sortstr key) ((org-node-create sortstr (org-id-new) key)) nil])

(I'm using elpaca to install org-node, org-node-fakeroam, and el-job from github; maybe I don't have these in the right order or something. I'm wondering if this related to dailies not currently being marked/font-locked on the calendar view.)

[meedstrom]

Hey Benjamin! Been on a vacation, but I’ll look into this today 😀

…

On Sun, Dec 8, 2024 at 01:33 Benjamin Slade ***@***.***> wrote: I seem to be getting org-node-related timer errors: Error running timer: (cl-no-applicable-method #[(sortstr key) ((if (fboundp 'org-node-fakeroam-daily-create) (org-node-fakeroam-daily-create sortstr key t) (error "Not installed: org-node-fakeroam"))) nil] comp--spill-lap-function #[(sortstr key) ((if (fboundp 'org-node-fakeroam-daily-create) (org-node-fakeroam-daily-create sortstr key t) (error "Not installed: org-node-fakeroam"))) nil]) Error running timer: (cl-no-applicable-method #[(node) ((let ((time (cdr (assoc "CREATION_TIME" (org-node-get-props node))))) (when (and time (not (string-blank-p time))) (cons time (org-node-get-id node))))) nil] comp--spill-lap-function #[(node) ((let ((time (cdr (assoc "CREATION_TIME" (org-node-get-props node))))) (when (and time (not (string-blank-p time))) (cons time (org-node-get-id node))))) nil]) Error running timer: (cl-no-applicable-method #[(sortstr key) ((org-node-create sortstr (org-id-new) key)) nil] comp--spill-lap-function #[(sortstr key) ((org-node-create sortstr (org-id-new) key)) nil]) (I'm using elpaca to install org-node, org-node-fakeroam, and el-job from github; maybe I don't have these in the right order or something. I'm wondering if this related to dailies not currently being marked/font-locked on the calendar view.) — Reply to this email directly, view it on GitHub <#76>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQNTTF57QMKF4Q3IGFIPXH32EOHWRAVCNFSM6AAAAABTGVYQSCVHI2DSMVQWIX3LMV43ASLTON2WKOZSG4ZDIOBXGM4TQNA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[meedstrom]

Would these changes solve the issue? e60db8b

[emacsomancer]

I still don't seem to be getting marked dates in the calendar

[meedstrom]

Oh, maybe with this? I'll add it in, thanks for mentioning.

(defvaralias 'org-node-series-that-marks-calendar 
             'org-node-seq-that-marks-calendar)

[meedstrom]

Checking in, do you get marked dates now?

[emacsomancer]

I do get marked dates now.

(I'm still getting the timer errors sometimes, but functionality doesn't seem otherwise impaired?)

[meedstrom]

Interesting problem. Now I understand my first fix would not have done anything.

Did a possible fix on a separate branch: 131059d

If you get time, maybe copy-paste that and see if the problem stops appearing!

---

As always, thanks for reporting. It's possible that other people are also seeing this error. Out of curiosity, what's your gc-cons-threshold?

[meedstrom]

I believe 0126d65 (1.9.36) makes it moot, so closing.

[emacsomancer]

Thanks, @meedstrom ! Yes, I've merged the latest now from MELPA, and these errors seemed to have disappeared. Cheers!

I was curious about the commit - you say "Give up native-compiling lambdas due to inconsistent support" - is it different versions of Emacs? Different versions of libjitgcc? Where there are differences? Or that details of different compiled lambdas are just differently amenable to native-compilation?

[meedstrom]

In my several months-old build of Emacs 30.0.50, I could do (native-compile (lambda ()).

In the just-releaded Emacs 30.1, it causes an error. The definition of native-compile doesn't appear to support anonymous lambdas, I'm guessing it was never really intended or not a priority. It needs a symbol with a function definition.

[emacsomancer]

Hmm, that's interesting. (I'm still on 30.0.93; need to upgrade when I get can around to it for Guix [have a custom build for Emacs with Lucid and some other things].)

(I don't understand the deep underpinning of native compilation well enough at this point to reason about what native-compile (lambda ()) would or should do. It would seem that (lambda ()) and (defun ()) should be able to be handled similarly. Is it just about whether there's a label to hang it on? Is their undefined behaviour that can arise otherwise?)

[meedstrom]

Essentially about the label, I think. The output of (lambda) is a function. The output of (defun foo) is a symbol 'foo. A side effect is giving that symbol a function binding (as opposed to a variable binding, which it can also have). If you do (symbol-function 'foo), then the output should look like the output of (lambda). More or less.

[meedstrom]

Well, maybe you already knew that. I'd wager the reason it doesn’t work for anonymous lambda if it’d rarely be used anyway.

[emacsomancer]

I suppose I'm wondering why unlabelled/anonymous functions wouldn't potentially benefit from native optimisation, but maybe there are technical details of nativecomp I'm not understanding.