I am brand new to Slime, not entirely new to Emacs. Trying to install Slime 2.0 in either Emacs 22 on XP or Emacs 21 on Cygwin, and with both I get the same two errors - "Lisp nesting exceeds max-lisp-eval-depth" and "Variable binding exceeds max-specpdl-size," both related to tramp-file-name-handler.
Attempting to increase values for these results in no improvement. Once values exceed 10000, Emacs predictably blows up. I have no idea how to set a backtrace for this error; setting up tramp error logging does nothing, probably because tramp isn't being started. No references that I can find in the Slime documentation for this problem.
Here are the relevant init settings for Emacs 22 on XP - nothing unusual so far as I can tell:
(add-to-list 'load-path "/L:/Free/Office/Contacts/Wanderlust/Hacking/lisp/slime/") ; your SLIME directory (setq inferior-lisp-program "C:/Program Files/acl80-express/allegro-ansi.exe") (require 'slime) (slime-setup)
Help would be appreciated ...
+ "Randy Burgess" public@raburgess.com:
| I am brand new to Slime, not entirely new to Emacs. Trying to | install Slime 2.0 in either Emacs 22 on XP or Emacs 21 on Cygwin, | and with both I get the same two errors - "Lisp nesting exceeds | max-lisp-eval-depth" and "Variable binding exceeds | max-specpdl-size," both related to tramp-file-name-handler.
I am entirely unfamiliar with this environment, so I cannot give concrete advice. However ...
| Attempting to increase values for these results in no improvement.
This is no surprise: Stack limits are usually generous enough, so a stack overflow generally implies an infinite recursion.
Try to set debug-on-error to t (M-x set-variable RET debug-on-error RET t RET). When the error occurs, you should get dumped in the emacs lisp debugger. There you can poke around if you wish, or just look at the call stack and see what functions are involved. You could try copying the relevant bits (only once around the infinite loop, please) and sending it to the list, and maybe someone can spot the problem.
- Harald
PS. You had the Reply-To field set to your email address. This practice is problematic on mailing lists, since those responding may not notice and so fail to send a copy of their response to the list.
-
Harald Hanche-Olsen -
Randy Burgess