public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Laurens Blankers <laurens@blankersfamily.com> To: cygwin-xfree@cygwin.com Subject: Suggestion for improving xinit 1.3.4 Date: Mon, 05 Jan 2015 11:46:00 -0000 [thread overview] Message-ID: <54AA7981.7080805@blankersfamily.com> (raw) Hi, 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]. 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] 3. Adding 'listen' option to the FAQ Consider adding something similar: Q: X server is no longer accepting client connections, how come? A: For security reasons, by default the X server no longer listen for tcp connections, if you really want this add '-listen' to the start-up parameters. Also see [6]. 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. I hope these suggestions don't require too much work. I think they would have a significant positive impact on UX. Laurens [1] https://cygwin.com/ml/cygwin-xfree/2015-01/msg00012.html [2] https://cygwin.com/ml/cygwin-xfree/2014-11/msg00029.html [3] https://cygwin.com/ml/cygwin-xfree/2014-12/msg00012.html [4] https://cygwin.com/ml/cygwin-xfree/2014-12/msg00013.html [5] https://cygwin.com/ml/cygwin-xfree/2014-12/msg00059.html [6] https://cygwin.com/ml/cygwin-xfree/2015-01/msg00013.html [7] http://semver.org/ -- 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 reply other threads:[~2015-01-05 11:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-05 11:46 Laurens Blankers [this message] 2015-01-05 17:43 ` Yaakov Selkowitz 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=54AA7981.7080805@blankersfamily.com \ --to=laurens@blankersfamily.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).