X-Recipient:	archive-cygwin AT delorie DOT com
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=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=xUOOsFV8p2sHBNZXBz9nNcLLMiQ=; b=a9T
	H6lCVUTjfRx5GVS8lggw10GJbbEX7IsvxVB3ROdIvMTXkKZYlgVdfLl95pe7Iuvd
	Nylb4e2cm9LgFF/c3MS7HGyhM2XDo/XZEN2SkmmEc9GRFMLekFK8K13W9cvzQ9nf
	IH2w2tPCklbRmDvvmZ9m47WFeUF7NpsrrjJLiKuo=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=vary, traction
X-HELO:	mail-qt0-f176.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=loZSbuyYy/FdgO97aY49zrxkP/08THmTlooCIOOsY8o=; b=jWs44myvXJiiASw0bZTPee6GDzw+cnF7DM8Dlt73y2fRgHcbWp/1hotHgatepmssPq fHzrQV/Nz488Jmo6QSshvWWZfLqAIKZOJQkw7tqHe6exmFuFi8cuHMs6/8BfMbq0VdmX 0VFnVMlVwWgDqFEWd2qCcMbpAsN3DKT+4f0VTQD9r7vzSvT6uBOzqWGRNBt/P91QZ6fq lXh+H6FiIvvODnQx4jXMOy+HBRt+L5Htw/GNLVoXAkHI6iJV/T9mvpViRO5YipYz4GOK x2IFvF72yr69wGzuDraoMA+4gNz+r8dfOCwokzIoPFe6xZ8dVKOw1K+Mk6rhr/wVtgOD Pthw==
X-Gm-Message-State:	AODbwcARg5xH6Qjj9c3oSVd0QXXJSXW0g0T28qKNv/ljKdFm2OcZx0Ta VLW7mUt/CFzR6rGp+A3ZoSWTKdL+7Kqh
X-Received:	by 10.200.11.202 with SMTP id p10mr4221830qti.221.1497003276059; Fri, 09 Jun 2017 03:14:36 -0700 (PDT)
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

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

- Raw text -