Re: vc-follow-symlinks confirm message is not read only

[Luc Teirlinck]

>From my previous message:

   In as far as the places where inhibit-read-only should be t, it must
   be t at least for the call to erase-buffer (unless one would change
   that function as suggested).  I guess it probably must be t at other
   places too, since otherwise it probably just would have been bound to
   t around that call.

I somehow forgot the obvious fact that inhibit-read-only must also
take care of read-only buffers.  (I was thinking of text properties).
So there definitely seem to be other places where inhibit-read-only
needs to be t, which of course does not mean that it has to be t over
the entire scope of the function.

Sincerely,

Luc.