public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: xinit is ignoring -displayfd option
Date: Wed, 06 Sep 2017 12:50:00 -0000	[thread overview]
Message-ID: <b89c4829-d627-5e31-0c60-3e462d619810@gmail.com> (raw)
In-Reply-To: <59AF8B3C.2080501@gmail.com>

On 9/6/2017 1:44 AM, Matt D. wrote:
> I'm not sure at what release this bug appeared as my .display already
> existed with the value '0' which masked the problem. When I ran xinit on
> a system without a .display already present caused some of my scripts to
> fail as this file is no longer created due to the wrong fd being used.
> 
> Here is the output of xinit:
> 
> https://pastebin.com/raw/HJB9WGk7
> 

I assume you want to point out the creation of "/home/.display" from the
xinit redirect.  You should have just said so.  You could have also just
pasted the contents of the output in the email instead of putting it in
pastebin.

<pastebin>
$xinit -- -multiplemonitors -multiwindow -clipboard -noprimary -dpi 96
-nolisten tcp -displayfd 3 3>"/home/.display"

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.19.2.0
OS: CYGWIN_NT-10.0-WOW DESKTOP-937VVAM 2.8.2(0.313/5/3) 2017-07-12 10:53
i686
OS: Windows 10  [Windows NT 10.0 build 15063] (WoW64)
Package: version 1.19.2-1 built 2017-03-09

XWin was started with the following command line:

X -multiplemonitors -multiwindow -clipboard -noprimary -dpi 96
 -nolisten tcp -displayfd 5
</pastebin>

-- 
cyg Simple

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2017-09-06 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-06  5:44 Matt D.
2017-09-06 12:50 ` cyg Simple [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:
  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=b89c4829-d627-5e31-0c60-3e462d619810@gmail.com \
    --to=cygsimple@gmail.com \
    --cc=cygwin@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).