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

From: "Roland Winkler" <[email-masked]>
Date: Mon, 2 Jun 2014 11:25:14 -0500

On Mon Jun 2 2014 Stefan Monnier wrote:
> > 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?
(Certainly, throwing an error makes sense for processes which do
create output in a read-only buffer.)

Roland