X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20091204181359.GB2976@ednor.casa.cgf.cx> References: <4B184E76.60909@tlinx.org> <416096c60912040946r2369f4c4i1f44d7d65320e7f7@mail.gmail.com> <416096c60912041003u18457d3ek85ec6b848dde4e8@mail.gmail.com> <20091204181359.GB2976@ednor.casa.cgf.cx> Date: Tue, 8 Dec 2009 10:05:55 +0000 Message-ID: <416096c60912080205m17a09a78sb001aca05b6179e9@mail.gmail.com> Subject: Re: Why does exiting bash window kill off Gvim? (Windows version, but X-would be same question) From: Andy Koppe To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 2009/12/4 Christopher Faylor: >>Hang on, if I do this: >> >>$ setsid gvim -display :0 & >> >>in a bash console and then close the console, gvim continues to work, >>so either setsid or gvim itself does detach from the console. > > That makes sense. =C2=A0Cygwin sends explicit SIGHUPs to other members of= the > console process group when it receives a CTRL_CLOSE_EVENT. =C2=A0setsid s= hould > fix that. > > You shouldn't need the '&' in the above scenario. =C2=A0Did that actually= make > a difference? I hadn't even tried without, and you're right, setsid doesn't wait for the program to finish anyway. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple