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 18:17:00 -0000	[thread overview]
Message-ID: <54AAD53C.8050403@cygwin.com> (raw)
In-Reply-To: <54AACD28.9060407@cygwin.com>

On 2015-01-05 11:43, Yaakov Selkowitz wrote:
> 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?

I could have startxwin check if ~/.startxwinrc is executable, and skip 
if it not, which might also cover many of these empty .startxwinrc's. 
OTOH all that might accomplish is trade the "why won't it start" for 
"why doesn't it respect my config". :-)

--
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/


  reply	other threads:[~2015-01-05 18:17 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
2015-01-05 18:17   ` Yaakov Selkowitz [this message]
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=54AAD53C.8050403@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: 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).