[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "Text is read-only" infinite loop (Carbon)
From: |
YAMAMOTO Mitsuharu |
Subject: |
Re: "Text is read-only" infinite loop (Carbon) |
Date: |
Wed, 24 Nov 2004 08:35:10 +0900 |
User-agent: |
Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3.50 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI) |
>>>>> On Mon, 22 Nov 2004 21:20:34 +0100, Magnus Henoch <address@hidden> said:
> I can reproduce this easier than it seemed - by trying to delete
> read-only text with M-DEL.
Thanks for the report. It was very helpful. It generates an error
because a read-only text remains in the " *code-conversion-work*"
buffer, and it prevents us from erasing the buffer in the next call of
`run_pre_post_conversion_on_str' (in coding.c) .
For example, the first evaluation of
(encode-coding-string (propertize (string (make-char 'latin-iso8859-1 33))
'read-only t) 'utf-8)
succeeds in producing "\302\241", but the second evaluation of the
same expression results in the "Text is read-only" error.
Since displaying menus or title bars now involves code conversions
from emacs-mule to utf-8 in some platforms, this error may occur on
menu activation or C-x 5 2.
YAMAMATO Mitsuharu
address@hidden
Re: "Text is read-only" infinite loop (Carbon), Richard Stallman, 2004/11/23