public inbox for
help / color / mirror / Atom feed
From: Jon Turney <>
Subject: Re: new start method questions
Date: Mon, 13 Jun 2016 13:07:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 10/06/2016 18:05, mathog wrote:
> On 09-Jun-2016 17:55, mathog wrote:
>> Last time around the start bat script was just:
>> @echo off
>> set CYGXTOP=%~dp0
>> C:
>> chdir "%CYGXTOP%\var\log\xwin"
>> move XWin.0.log.1 XWin.0.log.2
>> move XWin.0.log XWin.0.log.1
>> chdir "%CYGXTOP%\bin"
>> start Xwin :0 -multiwindow
>> Is there some reason that a similar cut down bat file would not work
>> with the current cygwin X11 server? (With "-listen tcp" plus a windows
>> firewall rule to only let it talk to localhost.)

Usually, the fastest way to answer that kind of question is to try it :)

> In a regular CMD shell navigated to the bin directory and did:
> start Xwin :0 -multiwindow -listen tcp
> and it worked.  So none of the current start script seems to be
> necessary if the only
> goal is to start the X11 server.  It seems to work normally, at least by
> the criterion that xdpyinfo returns the same information as for the
> other starts.

Yes, if running XWin doesn't actually start the server, that would be a bug

> On a related note - are there any situations where the X11 server itself
> (not something in its startup script) will start a subprocess and run a
> different binary?  For instance, some sort of font search operation, or
> perhaps some conditional load of an X11 feature which isn't normally
> started, or some funny kind of cut and paste operation on the Window side?

There are only 2 cases I can think of:

- The xserver runs xkbcomp during start up to compile the keyboard map
- Menu items in Xwinrc which use the EXEC instruction

Jon Turney
Volunteer Cygwin/X X Server maintainer

Unsubscribe info:
Problem reports:

      reply	other threads:[~2016-06-13 13:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 23:32 mathog
2016-06-10  0:55 ` mathog
2016-06-10  2:27   ` Marco Atzeri
2016-06-10 17:05   ` mathog
2016-06-13 13:07     ` Jon Turney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).