public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com> To: cygwin-xfree@cygwin.com Subject: Re: Suggestion for improving xinit 1.3.4 Date: Mon, 05 Jan 2015 17:43:00 -0000 [thread overview] Message-ID: <54AACD28.9060407@cygwin.com> (raw) In-Reply-To: <54AA7981.7080805@blankersfamily.com> On 2015-01-05 05:46, Laurens Blankers wrote: > As requested [1] a separate thread for suggesting improvements to xinit, > in order to solve some of the issues people have been having since the > release of 1.3.4-1 [2]. > > 1. Handling of empty .startxwinrc > Given the new behaviour of startxwin having an empty is never a correct > configuration. It would be really nice if startxwin could check for a > zero length .startxwinrc and in that case just start the X server > without any programs, as it used to do in 1.3.2-1. This would solve a > problem reported several times [3, 4] and also solve the problem of > having an icon on the task bar for 'sleep inf' [5]. And what if it's not zero-length but still blank? > 2. Adding a hint about 'sleep inf' to the FAQ > Not everyone reads the release notes, most people, when running into > problems will read the FAQ first. How about adding an entry similar to > this one: > > Q: startxwin exits immediately on start-up without error > A: ~/.startxwinrc must be executable and block or else X server will > exist, adding a 'sleep inf' to the end of the file should help, also see [2] Yes, something along these lines should be added to the FAQ soon. > 3. Adding 'listen' option to the FAQ See my response to your PuTTY thread. > 4. Semantic versioning > Signalling major changes in the version number makes it a lot easier to > find the problem, at least for me. Semantic versioning [7] suggest does > thing. Practically this would have mend calling the latest release > 2.0.0-1 rather than 1.3.4-1. No additional effort required, but a clear > signal to people to read the release notes. xinit -- the startx and xinit parts -- is an upstream X.Org package, and they determine the package version. The startxwin components are Cygwin-specific additions to the package, as they have been since we first released modular X11R7.4. Therefore, changing the version in this way isn't a viable option here. However, from personal experience, I disagree that a different version number would have made a bit of difference. Either people will read the announcements -- and the subject of mine should have indicated that this wasn't a routing update -- or they won't. -- Yaakov -- 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:[~2015-01-05 17:43 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-05 11:46 Laurens Blankers 2015-01-05 17:43 ` Yaakov Selkowitz [this message] 2015-01-05 18:17 ` Yaakov Selkowitz 2015-01-06 9:38 ` Laurens Blankers 2015-01-07 6:08 ` Yaakov Selkowitz 2015-01-07 21:39 ` Laurens Blankers
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=54AACD28.9060407@cygwin.com \ --to=yselkowitz@cygwin.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).