Subject: bug#17666: 24.3.91; [regression] call-process in read-only buffers

From: Stefan Monnier <[email-masked]>
Date: Mon, 02 Jun 2014 13:57:21 -0400

>> > evaluate the following with emacs -Q
>> > ;; running a process with no output via call-process
>> > ;; in any read-only buffer will do
>> > (with-temp-buffer
>> >   (let ((buffer-read-only t))
>> >     (call-process "true" nil t)))
>> > No problem with emacs 24.3
>> I do not remember this being changed consciously, but the change does
>> sound like a bug fix: you should bind inhibit-read-only if you want to
>> insert text into a read-only buffer, and call-process shouldn't be
>> an exception.
> But what is the problem if a process does not have any output?

Ah.. eh.. hmm.. yeah.. that case!
Well, then better make sure your process does output something!

        Stefan "who skipped the "true" part, obviously.  Sorry"