-
Notifications
You must be signed in to change notification settings - Fork 39
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
max-lisp-eval-depth problem #138
Comments
Could you share an example file that has this problem? |
This file below produces the error for me if I save it as 'test.groovy' and open it in Emacs.
|
The problem is that the error prevents the mode to run properly, e.g. some hooks and minor modes are not loaded |
Strange, but I could make a workaround by evaluating these:
This way it complains about company-mode-hook, but then loads company-mode fine, and I also get syntax coloring. If I leave the company-mode-hook out, then I get neither. |
I'm unable to get an error with that file. Could you try If you can get a traceback, please post it here. |
I tried this, but I don't get a Backtrace window. The error is shown in the minibuffer and in the Messages but that's it. |
What else is in your groovy-mode-hook and prog-mode-hook? Can you replicate the issue with |
groovy-mode-hook contains: I tried the procedure you insisted, but got the following error when trying to load groovy-mode.el: |
Sorry, I should have mentioned. When you start with |
Emacs version: 28.0.50
Sometimes when I open a groovy file, I get "File mode specification error: (error Lisp nesting exceeds 'max-lisp-eval-depth')" error in minibuffer.
Increased the max-lisp-eval-depth to 10000, but that didn't solve the problem.
Tried to debug, and the last function executed before the error was normal-mode, with something like "couldn't load files.el".
Due to the error, I don't get syntax coloring in groovy-mode. But if I M-x normal-mode after the error, I get my file colored (and another error message).
Please help investigating the problem.
The text was updated successfully, but these errors were encountered: