[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#5984: Crash displaying composed characters
From: |
Kenichi Handa |
Subject: |
bug#5984: Crash displaying composed characters |
Date: |
Sat, 01 May 2010 15:28:46 +0900 |
In article <jwvr5lw4qnn.fsf-monnier+gnus-read-ephemeral-bug@gnu.org>, Stefan
Monnier <monnier@IRO.UMontreal.CA> writes:
> > . Emacs then enters redisplay to display the echo area. As part of
> [...]
> > . Further down, autocmp_chars calls the value of
> > auto-composition-function:
> [...]
> > . Now the " *Echo Area0*" buffer holds a totally different text,
> > unbeknownst to autocmp_chars, which still passes the old values 32
> > and 33 to TEMP_SET_PT_BOTH:
> More generally, this Lisp code could modify any buffer, so preventing
> the load-messages is not a sufficiently reliable solution (tho it might
> be desirable in any case).
Yes, and this problem is not only in auto-composition. For
instance, evaluating this crashes Emacs.
(put-text-property 1 10 'display '(height (progn (delete-region 1 10))))
How about having a special mode in which any modifications
to buffers are silently ignored, and we run Lisp in that
mode in redisplay?
Another way is to check MODIFF before and after calling
Lisp, and if the current buffer is modified, restart the
redisplay... somehow.
---
Kenichi Handa
handa@m17n.org