This is the mail archive of the firstname.lastname@example.org
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: empty bash window
- To: John Collins <email@example.com>, firstname.lastname@example.org
- Subject: Re: empty bash window
- From: Charles Wilson <email@example.com>
- Date: Mon, 01 Mar 1999 12:36:47 -0500
- Delivered-To: firstname.lastname@example.org
- Delivered-To: mailing list email@example.com
- Mailing-List: contact firstname.lastname@example.org; run by ezmlm
- References: <DFCB901CFA52D211A35000104B2E651E59AE1D@valkyrie.is.com>
- Sender: email@example.com
- Sender: firstname.lastname@example.org
John Collins wrote:
> I'm working with a group that is in the process of migrating Java
> development to emacs/NT, JDE, and cygwin make. I've found that the JDE
> "build" command, which uses the emacs "compile" function, runs make as a
> subprocess. If you do this with the "standard" NT emacs shortcut, the
> underlying shell is the NT command processor, and make barfs. If you
> explicitly start emacs from bash, then everything works as expected.
> So, I tried modifying the shortcut for starting emacs to look like
> "bash -c emacs"
> and it works, except I get an extra, empty bash window.
> Now to the question: Is there a way to start emacs under bash without that
> extra window cluttering up the screen? Or do I need to re-define the compile
> command to use "bash -c make" instead of just make?
> John Collins
> KeyTech LLC
You could _try_ run.exe, which executes any console-mode program without
showing the console. It's available from
ftp://belgarion.resnet.gatech.edu/pub/run/run-1.1.4.tar.gz. It's licensed under
Want to unsubscribe from this list?
Send a message to email@example.com
- No Subject
- From: John Collins <firstname.lastname@example.org>