Re: M-x compile with input set to </dev/null as default

[Kevin Rodgers]

Dan Jacobson wrote:

> Just curious, why not run compile with input set to </dev/null as
> default, as one can't just answer any questions asked on the screen,
> e.g (compile "echo x=; read x").

Probably because people are more interested in adding the ability to
read user input in a *compilation* buffer.  I first posted a way to do
that back in October 1996 and recently updated it for Emacs 21:

        From: Kevin Rodgers <ihs_4664@yahoo.com>
        Newsgroups: gnu.emacs.help
        Subject: Re: comint-mode broken in GNU Emacs 21.2.1?
        Date: Thu, 18 Sep 2003 16:39:01 -0600
        Message-ID: <3F6A3405.8040609@yahoo.com>

Here's a link to that message:

http://www.google.com/groups?selm=3F6A3405.8040609%40yahoo.com

But 7 years ago I also submitted a patch that did exactly what you're
asking for:

        From: kevinr@ihs.com (Kevin Rodgers)
        Newsgroups: gnu.emacs.bug
        Subject: Re: standard input in *compile* buffers
        Date: Fri, 18 Oct 1996 07:50:11 -0600
        Message-ID: <199610181350.HAA03498@airedale.ihsyp>
        ...
        Here's a slightly improved version of the patch I submitted,
        which makes the redirection optional (controlled by the new
        variable compile- disable-input) as Karl suggested.  Its default
        value makes compile behave the same whether the platform
        supports asynchronous processes or not.

And here's a link to that message:

http://www.google.com/groups?selm=199610181350.HAA03498%40airedale.ihsyp


--
Kevin Rodgers