public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com> To: cygwin-xfree@cygwin.com Subject: RE: Automatic X server startup Date: Wed, 28 May 2014 12:57:00 -0000 [thread overview] Message-ID: <004001cf7a74$5c6b3ac0$1541b040$%fedin@samsung.com> (raw) In-Reply-To: <5384AD24.4080504@dronecode.org.uk> Hello! > I believe this is arranged using launchd on OS X, which listens on the > socket the X server will use, and starts the X server when something > connects. > > Unfortunately, there is no similar system facility on Windows. But it should be possible to make xlib a little bit more smart, isn't it ? It could automatically run X server when a connection is attempted but refused. So we would achieve the same effect as on MacOS. We could e. g. have some directory like /etc/X11/autostart, to be examined by xlib. If it detects that e. g. :0 screen is not accessible, it would attempt to look up 0.xlaunch file there and run "xlaunch -run /etc/X11/autostart/0.xlaunch" command. What do you think ? I could implement this idea if you have no time to work on that, i believe it should be very easy. > You can achieve a somewhat similar effect by copying the X server > shortcut to the startup group to start it automatically at login, at > the cost of slowing down system startup somewhat. Heh, it's already slow because of antivirus and other corporate stuff (i cannot disable it). Running on demand would be better. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia -- 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/
next prev parent reply other threads:[~2014-05-28 12:57 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-27 12:52 Pavel Fedin 2014-05-27 13:38 ` Eliot Moss 2014-05-27 15:20 ` Jon TURNEY 2014-05-28 12:57 ` Pavel Fedin [this message] 2014-06-02 13:57 ` Jon TURNEY 2014-07-03 22:54 ` Matt D.
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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='004001cf7a74$5c6b3ac0$1541b040$%fedin@samsung.com' \ --to=p.fedin@samsung.com \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe 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).