Re: problem saving history

[Stefan Monnier]

>> Try the set "Options => Enter Debugger on Error" and then reproduce the
>> error, this should put you in a *backtrace* buffer where you'll get a bit
>> more information.  If you don't understand this info, post it here.

> I have the same error. Doesn't really bother me, but it'd be nice not
> having to type "y" every time I quit emacs ;-)

> Here's the debug info:

> Debugger entered--Lisp error: (wrong-type-argument stringp \.\.\.)
>   signal(wrong-type-argument (stringp \.\.\.))
>   (if (y-or-n-p (format query ...)) nil (signal (car err) (cdr err)))
>   (condition-case err (funcall fun) (error (if ... nil ...)))
>   slime-repl-call-with-handler(slime-repl-save-merged-history "%S
> while saving the history. Continue? ")
>   slime-repl-safe-save-merged-history()
>   (progn (slime-repl-safe-save-merged-history))
>   (if (eq major-mode (quote slime-repl-mode)) (progn (slime-repl-safe-
> save-merged-history)))
>   (when (eq major-mode (quote slime-repl-mode)) (slime-repl-safe-save-
> merged-history))
>   (save-current-buffer (set-buffer b) (when (eq major-mode ...) (slime-
> repl-safe-save-merged-history)))
>   (with-current-buffer b (when (eq major-mode ...) (slime-repl-safe-
> save-merged-history)))
>   (while --cl-dolist-temp-- (setq b (car --cl-dolist-temp--)) (with-
> current-buffer b (when ... ...)) (setq --cl-dolist-temp-- (cdr --cl-
> dolist-temp--)))
>   (let ((--cl-dolist-temp-- ...) b) (while --cl-dolist-temp-- (setq
> b ...) (with-current-buffer b ...) (setq --cl-dolist-temp-- ...)) nil)
>   (catch (quote --cl-block-nil--) (let (... b) (while --cl-dolist-
> temp-- ... ... ...) nil))
>   (cl-block-wrapper (catch (quote --cl-block-nil--) (let ... ... nil)))
>   (block nil (let (... b) (while --cl-dolist-temp-- ... ... ...) nil))
>   (dolist (b (buffer-list)) (with-current-buffer b (when ... ...)))
>   slime-repl-save-all-histories()
>   run-hooks(kill-emacs-hook)
>   kill-emacs()
>   save-buffers-kill-emacs(nil)
>   call-interactively(save-buffers-kill-emacs)


> Does that give you any clues? (I don't have any idea where to begin...)

Looks like a problem in Slime.  Try to post this same info to their
mailing list.


        Stefan