This is the mail archive of the
mailing list for the Cygwin XFree86 project.
Re: Two questions
- To: <cygwin-xfree at cygwin dot com>
- Subject: Re: Two questions
- From: "ted byers" <ted dot byers at sympatico dot ca>
- Date: Fri, 14 Sep 2001 07:30:56 -0400
>> Not exactly. I was thinking only of using alt-f4 on what you identify as
>> the cmd window in which bash runs. But this no longer works if I have
>> startxwin.sh from that window. Also, if I have not run startxwin.sh, the
>> cmd-window closes when I issue the command 'exit', but this TOO no longer
>> works if I have run startxwin.sh. But this does not happen if I have
>> startx. It is this that I do not understand, and would like to fix.
> Oh, now I know what you mean. The problem is that bash had started some
> child processes, which run in the background. If they are still running,
> you can't close bash. If you shutdown XWin, then bash will exit and the
> window will close. There is no other way which can avoid this.
The question clearly is, therefore, where is the relevant difference between
startx and startxwin.sh? Because the problem exists with startxwin.sh but
not with startx. The problem must lie within startxwin since it happens
even if I just start startxwin.sh and then attempt to close it.