reddit / emacs

cannot run emacs without error

_The_Fizz_ · 2022-04-16 14:02
I'm not well versed in emacs. after the latest update, starting emacs prompts me with this message Warning (initialization): An error occurred while loading ‘/home/user/.emacs.d/init.el’: Wrong number of arguments: (3 . 4), 2 I then run emacs using emacs --debug-init, which gives me this message which I don't understand very clearly Debugger entered--Lisp error: (wrong-number-of-arguments (3 . 4) 2) #f(compiled-function (obsolete-name current-name when &optional docstring) "Make OBSOLETE-NAME a variable alias for CURRENT-NAME and mark it obsolete.\n\nWHEN should be a string indicating when the variable was first\nmade obsolete, for example a date or a release number.\n\nThis macro evaluates all its parameters, and both OBSOLETE-NAME\nand CURRENT-NAME should be symbols, so a typical usage would look like:\n\n (define-obsolete-variable-alias 'foo-thing 'bar-thing \"28.1\")\n\nThis macro uses `defvaralias' and `make-obsolete-variable' (which see).\nSee the Info node `(elisp)Variable Aliases' for more details.\n\nIf CURRENT-NAME is a defcustom or a defvar (more generally, any variable\nwhere OBSOLETE-NAME may be set, e.g. in an init file, before the\nalias is defined), then the define-obsolete-variable-alias\nstatement should be evaluated before the defcustom, if user\ncustomizations are to be respected. The simplest way to achieve\nthis is to place the alias statement before the defcustom (this\nis not necessary for aliases that are autoloaded, or in files\ndumped with Emacs). This is so that any user customizations are\napplied before the defcustom tries to initialize the\nvariable (this is due to the way `defvaralias' works).\n\nFor the benefit of Customize, if OBSOLETE-NAME has\nany of the following properties, they are copied to\nCURRENT-NAME, if it does not already have them:\n`saved-value', `saved-variable-comment'." #<bytecode -0x3f180d0dea7a25e>)('common-lisp-glossary-fun 'common-lisp-hyperspec-glossary-function) (define-obsolete-variable-alias 'common-lisp-glossary-fun 'common-lisp-hyperspec-glossary-function) eval-buffer(#<buffer *load*-52704> nil "/home/user/quicklisp/dists/quicklisp/software/slime-v2.26.1/lib/hyperspec.el" nil t) ; Reading at buffer position 45354 load-with-code-conversion("/home/user/quicklisp/dists/quicklisp/software/slime-v2.26.1/lib/hyperspec.el" "/home/user/quicklisp/dists/quicklisp/software/slime-v2.26.1/lib/hyperspec.el" nil t) require(hyperspec "lib/hyperspec") eval-buffer(#<buffer *load*-421049> nil "/home/user/quicklisp/dists/quicklisp/software/slime-v2.26.1/slime.el" nil t) ; Reading at buffer position 2866 load-with-code-conversion("/home/user/quicklisp/dists/quicklisp/software/slime-v2.26.1/slime.el" "/home/user/quicklisp/dists/quicklisp/software/slime-v2.26.1/slime.el" nil t) (slime-setup '(slime-fancy)) (let* ((quicklisp-slime-directory (quicklisp-slime-helper-slime-directory))) (add-to-list 'load-path quicklisp-slime-directory) (require 'slime-autoloads) (setq slime-backend (expand-file-name "swank-loader.lisp" quicklisp-slime-directory)) (setq slime-path quicklisp-slime-directory) (slime-setup '(slime-fancy))) eval-buffer(#<buffer *load*-130058> nil "/home/user/quicklisp/slime-helper.el" nil t) ; Reading at buffer position 1547 load-with-code-conversion("/home/user/quicklisp/slime-helper.el" "/home/user/quicklisp/slime-helper.el" nil nil) load("/home/user/quicklisp/slime-helper.el") eval-buffer(#<buffer *load*> nil "/home/user/.emacs.d/init.el" nil t) ; Reading at buffer position 6152 load-with-code-conversion("/home/user/.emacs.d/init.el" "/home/user/.emacs.d/init.el" t t) load("/home/user/.emacs.d/init" noerror nomessage) startup--load-user-init-file(#f(compiled-function () #<bytecode 0xcc1682654efebaa>) #f(compiled-function () #<bytecode -0x1f3c686ddc0cdc35>) t) command-line() normal-top-level() how should I edit the init file as to not have this error?
ieure · 2022-04-16 14:52
Looks like a bug in SLIME. Remove that stuff and report your issue to them.
_The_Fizz_ · 2022-04-16 15:23
thanks, removing the slime related lines does get rid of the error, should I email their mailing list on their website to report? and before I do so, is there a way I could make slime work without the error?
Alan_Shutko · 2022-04-16 16:31
Slime had an update to work with emacs 28. It looks like your copy of slime was downloaded with quicklisp. Perhaps updating quicklisp will fix it?
00-11 · 2022-04-16 16:33
https://emacs.stackexchange.com/q/71378/105