[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to debug Error during redisplay
From: |
Leo Liu |
Subject: |
Re: How to debug Error during redisplay |
Date: |
Sat, 12 Jan 2013 19:56:59 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.2.92 (OS X 10.8.2) |
On 2013-01-12 17:43 +0800, Eli Zaretskii wrote:
> I downloaded the current snapshot of slime from
> http://common-lisp.net/project/slime/. Is this the package you are
> talking about? The only *.el file that calls animate-string there is
> slime-banner.el:
>
> (defun slime-startup-message ()
> (when slime-header-line-p
> (setq header-line-format
> (format "%s Port: %s Pid: %s"
> (slime-lisp-implementation-type)
> (slime-connection-port (slime-connection))
> (slime-pid))))
> (when (zerop (buffer-size))
> (let ((welcome (concat "; SLIME " (or (slime-changelog-date)
> "- ChangeLog file not found"))))
> (if slime-startup-animation
> (animate-string welcome 0 0)
> (insert welcome)))))
>
> Is this the code that produced the redisplay error messages? If so, I
> cannot reproduce this on my machine. If this isn't the code in
> question, then please show a minimal code snippet using animate-string
> that does reproduce the problem. (It isn't right to let me guess like
> this, if you want the problem solved any time soon.)
Thanks for taking the trouble to investigate the issue further. I have
just spent an hour to come up with this reproduction recipe.
1. Install adaptive-wrap.el from ELPA
2. Install sbcl or clisp or any CL supported by slime
1. Emacs -q -l t.el (t.el assumes sbcl, which you may want to change)
2. M-x slime
My whole *Messages* buffer looks like this:
--------------------------------
For information about GNU Emacs and the GNU system, type C-h C-a.
`flet' is an obsolete macro (as of 24.3); use either `cl-flet' or `cl-letf'.
[11 times]
Polling "/var/folders/mf/8_qnj_n146d0wxb32wdnb9jh0000gn/T/slime.13675" .. 1
(Abort with `M-x slime-abort-connection'.)
Polling "/var/folders/mf/8_qnj_n146d0wxb32wdnb9jh0000gn/T/slime.13675" .. 2
(Abort with `M-x slime-abort-connection'.)
Polling "/var/folders/mf/8_qnj_n146d0wxb32wdnb9jh0000gn/T/slime.13675" .. 3
(Abort with `M-x slime-abort-connection'.)
Polling "/var/folders/mf/8_qnj_n146d0wxb32wdnb9jh0000gn/T/slime.13675" .. 4
(Abort with `M-x slime-abort-connection'.)
Connecting to Swank on port 60501..
Error during redisplay: (jit-lock-function 1) signaled (wrong-type-argument
stringp nil)
Error during redisplay: (jit-lock-function 520) signaled (wrong-type-argument
stringp nil)
Error during redisplay: (jit-lock-function 1) signaled (wrong-type-argument
stringp nil) [2 times]
Connected. Let the hacking commence!
--------------------------------
t.el
Description: t.el
- How to debug Error during redisplay, Leo Liu, 2013/01/11
- Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/11
- Re: How to debug Error during redisplay, Leo Liu, 2013/01/11
- Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/11
- Re: How to debug Error during redisplay, Leo Liu, 2013/01/12
- Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/12
- Re: How to debug Error during redisplay,
Leo Liu <=
- Re: How to debug Error during redisplay, Leo Liu, 2013/01/12
- Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/12
- Re: How to debug Error during redisplay, Leo Liu, 2013/01/12
- Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/12
- Re: How to debug Error during redisplay, Stephen Berman, 2013/01/12
- Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/12
Re: How to debug Error during redisplay, Stefan Monnier, 2013/01/11