This is the mail archive of the
cygwin-xfree
mailing list for the Cygwin XFree86 project.
RE: [ANNOUNCEMENT] [1.7] Updated: xinit-1.1.1-5
- From: "Phil Betts" <Phil dot Betts at ascribe dot com>
- To: <cygwin-xfree at cygwin dot com>
- Date: Thu, 1 Oct 2009 14:18:51 +0100
- Subject: RE: [ANNOUNCEMENT] [1.7] Updated: xinit-1.1.1-5
- References: <4AC45795.5070305@alice.it> <4AC4A340.9060001@cwilson.fastmail.fm>
- Reply-to: <cygwin-xfree at cygwin dot com>
- Reply-to: cygwin-xfree at cygwin dot com
Charles Wilson wrote:
> Angelo Graziosi wrote:
>
>> In 'startxwin.bat' I see:
>>
>> %RUN% bash -l -c "XWin -multiwindow -clipboard -silent-dup-error"
>>
>> Shouldn't it be
>>
>> %RUN% bash -l -c "XWin -multiwindow -clipboard -silent-dup-error &" ?
>
> No, "run" implicitly puts the target in the background, unless you add
> the '-w' (wait) option.
I think Angelo was trying to avoid having an unnecessary bash process
hanging around. Bash is only used to prepare the environment, so why
not do it like this instead:
%RUN% bash -l -c "exec XWin -multiwindow -clipboard -silent-dup-error"
i.e. the bash process is replaced by XWin rather than spawning a new
process, putting it in the background, then exiting. Under *IX, this
is usually more efficient than Angelo's method, but I don't know if
this is true under cygwin, given the complexity of getting exec/fork
etc. to work under Windows.
Phil
--
This email has been scanned by Ascribe Ltd using Microsoft Antigen for Exchange.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/