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: Why does exiting bash window kill off Gvim? (Windows version, but X-would be same question)


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. ÂCygwin sends explicit SIGHUPs to other members of the
> console process group when it receives a CTRL_CLOSE_EVENT. Âsetsid should
> fix that.
>
> You shouldn't need the '&' in the above scenario. ÂDid 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


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