This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Ctrl-C will not kill a process started from cygwin shell

Alex Worden wrote:

I'm sorry if this is an obvious question but I searched and couldn't
find an obvious answer and wasn't sure what to search for...

It seems that some processes I start from a cygwin shell start in the
foreground - whereas if I start them from a cmd shell they start in
the background. (I know I can append an & but that's not the point
here). One process I know of in particular is my favoured Micro Emacs
editor (available at When this starts in the
foreground from cygwin, even Ctrl-C will not kill the process. What
determines this behavior and can I do anything about it.

I ask because more importantly, I am running into issues running Maven
tasks that do not return to the shell after completion. The only
option available to be is to kill the entire cygwin shell.

Please can someone explain what might be happening here, or point me
at documentation on this subject.

You're much better off directing these kinds of questions to the provider of the package. Discussion of external packages is not wholly on-topic here.

My WAG on your CTRL-C problems, based on lack of input about your
environment, you don't have 'tty' in your CYGWIN environment variable.

Larry Hall                    
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746


A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]