DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org C3F70393D019
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: Starting xterm as a DOS Command Prompt one-liner
Thread-Topic: Starting xterm as a DOS Command Prompt one-liner
Thread-Index: AdbD0UVfjtjMLqouTSa4HGt2eUyqVw==
Date: Thu, 26 Nov 2020 09:08:46 +0000
Message-ID: <DB6PR03MB301397DDC03897EB4A7D64A9A4F90@DB6PR03MB3013.eurprd03.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: d5c38b5b-dd20-46da-c677-08d891eae18a
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Nov 2020 09:08:46.4228 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1EUR05HT226
X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT,
 FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_PASS, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: cygwin@cygwin.com
X-Mailman-Version: 2.1.29
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: Fergus Daly via Cygwin <cygwin@cygwin.com>
Reply-To: Fergus Daly <fergusd84@outlook.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces@cygwin.com>

This one-line DOS command to start an xterm terminal:
D:\cygwin> bin\run bin\XWin -clipboard -nolock -multiwindow 2> nul & 
timeout 4 > nul 2> nul & 
bin\xterm -display :0.0 2> nul & 
bin\kill -KILL -- -1
(broken here after each "&" for clarity of presentation only) works, and is a
neat and convenient alternative to starting xterm at the bash or mintty prompt
with the single line
$ /bin/xinit /bin/xterm -- -nolock -multiwindow 2> /dev/null
(The "> nul" phrases in all the above just suppress notifications.)
Question 1:
I find the timeout .. chunk necessary to give XWin enough time to load
before the xterm .. chunk draws upon it.
Is there a different conjunction to "&" that says "wait till this is
enacted before moving on" (which is actually what I thought "&" did!)?
Question 2:
The final kill .. chunk only operates after the xterm terminal is closed,
and its purpose is to kill XWin, which otherwise hangs about.
Is there some other way of assuring that the un-needed XWin is killed,
maybe (I dunno) by adding a qualifier to the initial "run XWin" chunk?
Thank you!

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