Re: "Text is read-only" infinite loop (Carbon)

[Magnus Henoch]

Reiner Steib <address@hidden> writes:

> On Mon, Nov 22 2004, Magnus Henoch wrote:
>
>> (defun trigger-bug ()
> [...]
>> I switch to *scratch*, and type M-x trigger-bug.  If I hit DEL, I get
>> an error as expected, but things continue to work.  If I hit M-DEL
>
> Which function is bound to `M-DEL' in your build?  For me it runs
> `down-list'[1] which doesn't make much sense here.

It's `backward-kill-word'.

Thinking about it, one difference between `delete-backward-char' and
`backward-kill-word' is that the latter puts the removed text in the
kill ring.  But trigger-bug can't be simplified to (kill-new
(propertize "Delete this string" 'read-only t)).

[...]

> After loading your code and calling M-x trigger-bug RET and doing some
> random Copy&Paste commands, I can no longer create new frames with
> `C-x 5 2'.  In the message buffer I get: "x-create-frame-with-faces:
> Text is read-only" but Emacs doesn't hang.

Sometimes C-x 5 2 finds the loop for me - a new frame is created, but
Emacs does nothing but beeping and showing "Text is read-only" in the
echo area - but not consistently.

Magnus