Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<DFCB901CFA52D211A35000104B2E651E59AE1D@valkyrie.is.com>
From:	John Collins <jcollins AT key-tech DOT net>
To:	"'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
Date:	Mon, 1 Mar 1999 10:19:31 -0600
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2232.9)

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?

Thanks.

John Collins

KeyTech LLC


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -