* problem saving history
@ 2007-07-25 8:29 Karol.Skocik
2007-07-25 16:51 ` Stefan Monnier
0 siblings, 1 reply; 4+ messages in thread
From: Karol.Skocik @ 2007-07-25 8:29 UTC (permalink / raw)
To: help-gnu-emacs
Hi guys,
I have a problem which is driving me nuts and can't find anything
with google. When I edit some file or work in Slime REPL and close
emacs, I get this error:
"Wrong type argument: stringp, \\.\\.\\." while saving history
I was trying to locate which variable (or something else) holds the
location of history file (or does it work in completely different
way?) but my emacs-lisp-fu equals to almost zero.
I have emacs 22.1/gentoo x64.
Can some good soul give me some advice?
Thank you!
Karol
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: problem saving history
2007-07-25 8:29 problem saving history Karol.Skocik
@ 2007-07-25 16:51 ` Stefan Monnier
2007-08-31 14:37 ` Kevin Brubeck Unhammer
0 siblings, 1 reply; 4+ messages in thread
From: Stefan Monnier @ 2007-07-25 16:51 UTC (permalink / raw)
To: help-gnu-emacs
> I have a problem which is driving me nuts and can't find anything
> with google. When I edit some file or work in Slime REPL and close
> emacs, I get this error:
> "Wrong type argument: stringp, \\.\\.\\." while saving history
Looks like some code trie to save some kind of history (maybe history
variables) and it does it by pretty-printing the value but the value is not
fully printed because it's too long so it ends up with a `...' which later
causes the above error.
> I was trying to locate which variable (or something else) holds the
> location of history file (or does it work in completely different
> way?) but my emacs-lisp-fu equals to almost zero.
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.
Stefan
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: problem saving history
2007-07-25 16:51 ` Stefan Monnier
@ 2007-08-31 14:37 ` Kevin Brubeck Unhammer
2007-09-07 5:07 ` Stefan Monnier
0 siblings, 1 reply; 4+ messages in thread
From: Kevin Brubeck Unhammer @ 2007-08-31 14:37 UTC (permalink / raw)
To: help-gnu-emacs
Stefan Monnier skreiv:
> 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...)
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: problem saving history
2007-08-31 14:37 ` Kevin Brubeck Unhammer
@ 2007-09-07 5:07 ` Stefan Monnier
0 siblings, 0 replies; 4+ messages in thread
From: Stefan Monnier @ 2007-09-07 5:07 UTC (permalink / raw)
To: help-gnu-emacs
>> 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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-09-07 5:07 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-07-25 8:29 problem saving history Karol.Skocik
2007-07-25 16:51 ` Stefan Monnier
2007-08-31 14:37 ` Kevin Brubeck Unhammer
2007-09-07 5:07 ` Stefan Monnier
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).