DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=ANLiGtVe6wCNR7t3fXEyML1i7/0Iz
	FJKKZuxUnTTiqjBtw8leVdDxl9/suaaH1IatUpC5lB2xTgjcvYg7zAR3WAtSCCdE
	tUtJcfuW1ZUQIQme0+rWr+B0TBV/DZcc2FTQqWmKMhxwW3I3e814vGiQbJu7yOzi
	KJE3JXVEmD9vBA=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
From: Ugly Leper <ugly DOT leper AT gmail DOT com>
Date: Fri, 9 Jun 2017 11:14:35 +0100
Message-ID: <CAKqBF1jvZT1ZT30Wcj7x6_o83e4F2Wc2MCpW_o+cwrzVh_V=TQ@mail.gmail.com>
Subject: Re: Starting a xterm window
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="UTF-8"

>> /usr/bin/xterm: Xt error: Can't open display: :0.0
>> /usr/bin/xterm: DISPLAY is not set

Thanks for all suggestions. Both the following fragments seem to work
flawlessly. Both incorporate a waiting time for XWin to gain traction
before xterm is called:

1. Starting a xterm console from a .cmd file in a Windows Command
Prompt box: include the lines

bin\run bin\XWin -clipboard -nolock -multiwindow 2>nul
timeout 2 > nul 2> nul
bin\xterm -display :0.0

2. Starting a xterm console from a script in a bash (or mintty) shell:
include the lines

run XWin -clipboard -nolock -multiwindow 2>/dev/null &
sleep 2
/bin/xterm -display :0.0

You can vary the pause e.g. timeout 3 or sleep 4. Maybe as brief a
fuse as timeout 1 or sleep 1 will be adequate; but that would make me
nervy about getting the same failure as in >> at the top of this post.

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