Re: toggle-read-only should not give compilation warnings

[Stefan Monnier]

>> Once we're sure that the remaining calls to toggle-read-only are all
>> "correct", we should try to understand why that is and provide some
>> alternative function for that (and make toggle-read-only use that
>> function, of course).
> It's not difficult to see why the remaining calls are correct: they want
> to do the same thing as C-x C-q, either acting on a different buffer or
> with a different interactive invocation.  Examples include
> mode-line-toggle-read-only and Buffer-menu-toggle-read-only.
> Adding another function, rather than simply using toggle-read-only, is
> an unnecessary level of indirection.

Even better.


        Stefan