alright, really quick test then.

does evaluating this elisp (e.g. in your *scratch*buffer) throw an error?

(encode-time '(0 0 0 1 1 1900 nil nil t))


EDIT: didn’t spot that it was the exact line Emacs was complaining about in your photo.

arf, i spotted that the standard osc package (which i only depend on as a “bonus” for triggering buttons / encoders remotely) does some unholy stuff (negative unix timestamps).

it works on my x86_64 Linux station but i had to fork the lib in my Windows install, and it appears ARM builds don’t like that either.

guess i’ll remove the dep and submit a bug report (which is cumbersome for Emacs “standard” packages IIRC).


EDIT2: done :heavy_check_mark:

@xmacex you may have to delete the ~/.emacs.d/elpa/norns-<version> folder to remove the error and force package.el to refetch the package at startup.

3 Likes