From: Chong Yidong <cyd@stupidchicken.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 5984@debbugs.gnu.org, Andreas Schwab <schwab@linux-m68k.org>
Subject: bug#5984: Crash displaying composed characters
Date: Sun, 07 Aug 2011 15:45:29 -0400 [thread overview]
Message-ID: <874o1t80py.fsf@stupidchicken.com> (raw)
In-Reply-To: <CAAeL0ST1ye62t4tjh5fc7cF0OqN6HEsCRXA4BJu6bGtu82pmzA@mail.gmail.com> (Juanma Barranquero's message of "Wed, 6 Jul 2011 04:28:38 +0200")
Juanma Barranquero <lekktu@gmail.com> writes:
> (Just pinging; the workaround was installed in 23.X, I think, but the
> crash still happens in 24.0.50.)
A change to autocmp_chars in the trunk undid the workaround. I've fixed
that.
As to the larger question of how to handle composition or redisplay
functions that modify the buffer, I still don't see any good solution.
Forbidding them from modifying buffers entirely is no good, because
fontification functions need to be able to change text properties.
I will, however, install a few additional ad-hoc fixes on the trunk to
inhibit crashes like
(put-text-property 1 10 'display '(height (progn (delete-region 1 10))))
next prev parent reply other threads:[~2011-08-07 19:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 13:42 bug#5984: Crash displaying composed characters Juanma Barranquero
2010-04-20 15:06 ` Eli Zaretskii
2010-04-20 15:48 ` Juanma Barranquero
2010-04-20 16:07 ` Eli Zaretskii
2010-04-20 18:38 ` Glenn Morris
2010-04-20 17:29 ` Eli Zaretskii
2010-04-20 17:33 ` Juanma Barranquero
2010-04-20 17:52 ` Eli Zaretskii
2010-04-20 18:43 ` Lennart Borgman
2010-04-20 19:18 ` Eli Zaretskii
2010-04-20 20:38 ` Andreas Schwab
2010-04-21 10:48 ` Juanma Barranquero
2010-04-21 12:33 ` Andreas Schwab
2010-04-21 17:21 ` Juanma Barranquero
2010-04-23 9:17 ` Eli Zaretskii
2011-07-06 2:28 ` Juanma Barranquero
2011-08-07 19:45 ` Chong Yidong [this message]
2011-11-23 3:14 ` Juanma Barranquero
2011-11-23 6:47 ` Chong Yidong
2010-04-30 20:47 ` Stefan Monnier
2010-05-01 6:09 ` Eli Zaretskii
2010-05-01 6:28 ` Kenichi Handa
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874o1t80py.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=5984@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--cc=schwab@linux-m68k.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).