This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-26
Channels
- # announcements (28)
- # asami (13)
- # babashka (10)
- # beginners (170)
- # boot (1)
- # calva (35)
- # cider (21)
- # circleci (13)
- # clara (6)
- # clj-http (1)
- # clj-kondo (29)
- # cljdoc (5)
- # clojure (89)
- # clojure-czech (2)
- # clojure-europe (20)
- # clojure-france (16)
- # clojure-nl (6)
- # clojure-uk (5)
- # clojurescript (80)
- # community-development (6)
- # conjure (13)
- # cursive (18)
- # datascript (9)
- # datomic (1)
- # duct (1)
- # gratitude (2)
- # helix (7)
- # jobs (2)
- # kaocha (3)
- # lsp (22)
- # malli (5)
- # meander (1)
- # other-languages (34)
- # pathom (18)
- # polylith (24)
- # quil (10)
- # re-frame (5)
- # releases (1)
- # remote-jobs (4)
- # reveal (7)
- # shadow-cljs (8)
- # tools-deps (53)
I upgraded my packages yesterday (I’m using Doom Emacs, so doom upgrade
), and now I get an error when opening clj files or trying to launch cider: Error (clojure-mode-hook): Error running hook "clj-refactor-mode" because: (file-missing Cannot open load file No such file or directory cider-jar)
. Googling the error message did not help that much, do you have any pointers for me?
https://github.com/clojure-emacs/cider/blob/master/cider-jar.el is new, I'd make sure that your cider.el is the latest snapshot
Hmmm have to dig into that, everything regarding clojure and cider was managed by doom until now and I never had to do anything manually.
Did you restart Emacs after the package update? From time to time this fixes problems with package.el.
@U45T93RA6 Thanks for the help, got a starting point! cider-jar.el is in the repository, that looks fine to me.
@U051BLM8F Yes, Emacs was restarted. Also cleaned out the repositories folder and ran doom sync
again
Yes.
The cider
repo in .emacs.d/.local/straight is on 0a9d0ef429e76ee36c34e116c4633c69cea96c67
> Reinstalling packages manually also helps. That did the trick for me. I’d like to know the root cause and might look into it again later, but for now I needed everything to work again. Thanks for your help!
(for which the fix is removing all .elc files recursively within .emacs.d prior to starting Emacs - it's always a harmless step)
I think removing a package also removes its bytecode, but I might be mistaken. At any rate - such issues with bytecode that didn't get properly recompiled are very common.
Might fit these messages, I am just seeing right now?
definitely :) I'd guess that those messages would go away on subsequent Emacs sessions as the code get compiled again
Ha, learned something. Will do the cleanup of .elc files as you suggested, thanks!
:) Perhaps doom or straight.el maintainers would appreciate an issue report so that they can improve .elc handling
Absolutely, will try to write down the steps I did and the results 👍