From: Eli Zaretskii <eliz@gnu.org>
To: Leo Liu <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: How to debug Error during redisplay
Date: Sat, 12 Jan 2013 11:43:06 +0200 [thread overview]
Message-ID: <83a9seu47p.fsf@gnu.org> (raw)
In-Reply-To: <m24ninm0qx.fsf@gmail.com>
> From: Leo Liu <sdl.web@gmail.com>
> Date: Sat, 12 Jan 2013 13:25:10 +0800
>
> >> So this is triggered by animate-string which slime uses. Weirdly, the
> >> same code doesn't have this error in 24.2.
> >
> > Which code is that? can you show it? Or does any use of
> > animate-string trigger these messages?
>
> I mean the slime package, the same one running in 24.2 and 24.2.92.
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.)
> It seems to me that in 24.2.92, the code is able to continue without
> waiting for animate-string to finish. It feels more responsive.
I don't see how that could be true, but maybe I'm missing something.
In any case, is this a separate problem?
next prev parent reply other threads:[~2013-01-12 9:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 9:03 How to debug Error during redisplay Leo Liu
2013-01-11 10:25 ` Eli Zaretskii
2013-01-11 11:02 ` Leo Liu
2013-01-11 14:08 ` Eli Zaretskii
2013-01-12 5:25 ` Leo Liu
2013-01-12 9:43 ` Eli Zaretskii [this message]
2013-01-12 11:56 ` Leo Liu
2013-01-12 12:03 ` Leo Liu
2013-01-12 13:49 ` Eli Zaretskii
2013-01-12 13:58 ` Leo Liu
2013-01-12 14:31 ` Eli Zaretskii
2013-01-12 17:17 ` Stephen Berman
2013-01-12 12:30 ` Eli Zaretskii
2013-01-11 14:56 ` Stefan Monnier
2013-01-12 5:26 ` Leo Liu
2013-01-12 13:08 ` Stefan Monnier
2013-01-12 13:38 ` Leo Liu
2013-01-12 13:52 ` Eli Zaretskii
2013-01-12 14:07 ` Leo Liu
2013-01-12 14:38 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a9seu47p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sdl.web@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.