From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: M-x compile with input set to </dev/null as default
Date: Mon, 13 Oct 2003 10:07:24 -0600 [thread overview]
Message-ID: <3F8ACDBC.2070108@yahoo.com> (raw)
In-Reply-To: mailman.1519.1065829929.21628.bug-gnu-emacs@gnu.org
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
next parent reply other threads:[~2003-10-13 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1519.1065829929.21628.bug-gnu-emacs@gnu.org>
2003-10-13 16:07 ` Kevin Rodgers [this message]
2003-10-14 19:49 ` M-x compile with input set to </dev/null as default Dan Jacobson
2003-10-10 6:26 Dan Jacobson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F8ACDBC.2070108@yahoo.com \
--to=ihs_4664@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).