This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: 6.7.0.0 XWin w/out -nodecoration running in background doesn't display anything
- From: Rudolf Kollien <Rudolf dot Kollien at kollien dot de>
- To: cygwin-xfree at cygwin dot com
- Date: Fri, 9 Apr 2004 01:15:47 +0200
- Subject: Re: 6.7.0.0 XWin w/out -nodecoration running in background doesn't display anything
- Organization: www.kollien.de
- References: <200404082108.26908.Rudolf.Kollien@medas.de> <4075AD44.6080901@msu.edu>
- Reply-to: cygwin-xfree at cygwin dot com
- Reply-to: Rudolf dot Kollien at kollien dot de
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Harold,
sorry, if my question sounds stupid, but... when i can't use run in a batch
why there is "run" used in the startxdmcp.bat? It does the job as requested.
But only with "-nodecorations". Why can a window without border and titlebar
can be used, but a "normal" window not?
I don't want to compare to the old XFree86 (i'm glad about the new project)
but once upon a time there where the same problem but was gone long ago.
I will try the hint from David Rothenberger with "setsid" (never heared
about). Sound's good.
The problem is, that when the controlling window ist closed, the whole
X-session gets killed. I i know my users: the will close this "unneccessary"
window.
Am Donnerstag, 8. April 2004 21:51 schrieb Harold L Hunt II:
> Yeah, you can't use "run" in the batch file... you have to use "start"
> instead. I noticed this right before the release, but I don't have a
> permanent solution yet. We had to switch from "start" to "run" because
> "start" doesn't prevent a DOS box from being displayed and because we
> switched XWin.exe from not displaying a DOS box by default to displaying
> a DOS box by default. The reason for this is that the new logging
> facility allows sending messages both to standard output and to a log
> file if one is opened sometime after the server starts (message have to
> be cached until that point since they would otherwise be lost since the
> log file isn't open yet). The nicest thing about this is that people
> running "XWin -help" will now see the help output instead of having to
> open /tmp/XWin.log to see the output.
>
> What is the permanent solution to the problem? I don't know. I think
> it may be time to finish writing the batch file that just launches a
> bash shell script, but I haven't got time to work on that today.
>
> Harold
-----BEGIN PGP SIGNATURE-----
iD8DBQFAdd0ozOHTWsKaqE0RAhnsAJ9PM2jUh0CdZIvt1sWXXgQ/MAfgkQCgoid1
K7ioTXTqK3f5Pl4V6NIg+MI=
=gqaK
-----END PGP SIGNATURE-----