-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Symbol’s function definition is void: treemacs-define-leaf-node #84
Comments
The issue goes away if I roll back treemacs to commit This suits as a workaround -- I'll just pin treemacs to an older commit. But it might be a good heads up for the next release. |
Probably related issue on treemacs here. |
Final note on this, it looks like treemacs-define-leaf-node-type is the intended replacement for this obsolete macro, but the arguments are different enough that I couldn't come up with a patch without knowing a lot more about how this is being used. |
The old API is there, just not loaded by default. Requiring |
Could we do what this comment describes to solve this? lsp-metals/lsp-metals-treeview.el Lines 651 to 661 in 6af7018
|
Thanks @jcazevedo , I have solved it temporarily by adding
to |
I got bit by this too. |
#85 merged. |
I recently did a fresh install of doomemacs again but realized that I was facing this issue. Just came here to know what do you think? Should we check if there are any other plugins being affected? |
Describe the bug
I use straight.el on emacs 28.2, so I'm running the latest master version of metals. I'm getting the following error on start up of emacs:
Error (use-package): lsp-metals/:catch: Symbol’s function definition is void: treemacs-define-leaf-node
And a similar error when metals tries to start (when I open a Scala file):
Error running timer: (void-function treemacs-define-leaf-node)
This might be related to #81, because I see the following error just before:
Eager macro-expansion failure: (wrong-number-of-arguments (1 . 1) 0)
To Reproduce
I will attempt to come up with a simple series of steps, but my configuration and, specifically, the lsp start up module is here.
I get the same error on emacs start if I strip absolutely everything else from my
init-lsp.el
except:With that configuration, I just have to start emacs or try to start metals on any scala file to reproduce.
Expected behavior
lsp-metals to compile and start.
The text was updated successfully, but these errors were encountered: