This is the mail archive of the email@example.com
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]
- To: "'firstname.lastname@example.org'" <email@example.com>
- From: John Collins <firstname.lastname@example.org>
- Date: Mon, 1 Mar 1999 10:19:31 -0600
- Delivered-To: email@example.com
- Delivered-To: mailing list firstname.lastname@example.org
- Mailing-List: contact email@example.com; run by ezmlm
- Sender: firstname.lastname@example.org
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?
Want to unsubscribe from this list?
Send a message to email@example.com