pnaranja · 2022-07-19 18:34
I updated some packages which included updating the dependency compat.el to [28.1.2.0](https://github.com/phikal/compat.el/releases/tag/28.1.2.0)
When I try to invoke an org-roam command I see the error:
Symbol’s function definition is void: compat--inhibit-prefixed
Has anyone seen this issue?
I'm using Emacs 29.0.50 and Org-roam 20220621.527
​
​
***One Solution:***
*I was able to use org-roam after recompiling all my packages.*
*Used command:*
*(byte-recompile-directory package-user-dir nil 'force)*
grtcdr · 2022-07-19 19:18
Are you by any chance modifying the PATH variable from within Emacs?
I have a feeling this is the root of the issue, because I recently came across this exact error, and it turned out that removing the snippet which modified my PATH fixed it for me.
pnaranja · 2022-07-19 19:26
I just commented out all the commands in my init.el that deals with my PATH and restarted my Emacs. I still get the same error when trying an Org-Roam command
`;; Get env vars from shell`
`;; (use-package`
`;; exec-path-from-shell`
`;; :commands exec-path-from-shell`
`;; :ensure t`
`;; )`
`;; Add to Path`
`;(setq exec-path (append exec-path '("/usr/local/bin")))`
`;; On OS X, an Emacs instance started from the graphical user`
`;; interface will have a different environment than a shell in a`
`;; terminal window, because OS X does not run a shell during the`
`;; login. Obviously this will lead to unexpected results when`
`;; calling external utilities like make from Emacs.`
`;; This library works around this problem by copying important`
`;; environment variables from the user's shell.`
`;; https://github.com/purcell/exec-path-from-shell`
`;; (when (memq window-system '(mac ns x))`
`;; (exec-path-from-shell-initialize))`
Scr0f3 · 2022-07-19 20:00
I had this issue earlier today and following the advice from [https://emacs.stackexchange.com/questions/72655/after-updating-my-packages-two-packages-are-not-working-anymore-how-to-solve-t](https://emacs.stackexchange.com/questions/72655/after-updating-my-packages-two-packages-are-not-working-anymore-how-to-solve-t) I re-byte compiled everything (which triggered fresh native compilations too) and the problem went away
Sudo_Brew · 2022-07-19 20:09
Started having this problem via Magit as well, and this solution also fixed it for me. I use straight.el though, so I just deleted the whole of `straight/build/` and let it rebuild, since I don't know what other packages could have been affected.
grtcdr · 2022-07-19 20:13
:( That's a bummer.
That's all I've got, I really wish you the best of luck in fixing this, because this issue made my Emacs unusable.
guitmz · 2022-07-19 20:24
Had the same issue yesterday with a bunch of packages out of the blue. Reinstalled everything in my eMacs folder and it is working now
pnaranja · 2022-07-19 20:31
Thank you everyone for the help! After the recompile, I was able to use org-roam.
Used command:
`(byte-recompile-directory package-user-dir nil 'force)`
grtcdr · 2022-07-19 21:31
Well that's wonderful to hear!
I highly recommend editing the post and linking to this comment. I'm sure others will find it useful, given there's a sizeable chunk of people with the same issue.
emgee_1 · 2022-07-21 07:10
I had this problem too (could not use any consult package. )
M-x package-reinstall compat
fixed it for me