From: Fergus Daly <fergusd84@outlook.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: Starting xterm as a DOS Command Prompt one-liner
Date: Sat, 28 Nov 2020 14:14:44 +0000 [thread overview]
Message-ID: <DB6PR03MB3013F3437D4E4667DDC41CC3A4F70@DB6PR03MB3013.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <DB6PR03MB301397DDC03897EB4A7D64A9A4F90@DB6PR03MB3013.eurprd03.prod.outlook.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, ..
As a trivial postscript: starting xterm from Windows with the single line
above is as frugal a start-up as any I have come across: ps gives
PID PPID PGID WINPID TTY UID STIME COMMAND
1122 1121 1122 7232 pty0 197609 13:57:34 /usr/bin/ps
1120 1 1120 12216 cons0 197609 13:57:32 /usr/bin/xterm
1115 1 1115 11964 ? 197609 13:57:30 /usr/bin/XWin
1121 1120 1121 4228 pty0 197609 13:57:32 /usr/bin/bash
i.e. just 1 x bash + 1 x XWin + 1 x xterm.
Even the one-line xterm startup
$ xinit xterm -- -nolock -multiwindow
from a bash shell, recently shared here, gives the somewhat lengthy
PID PPID PGID WINPID TTY UID STIME COMMAND
1745 1739 1745 3548 ? 197609 14:01:42 /usr/bin/xterm
1740 1739 1740 6564 cons0 197609 14:01:41 /usr/bin/XWin
1737 1 1737 10976 cons0 197609 13:59:39 /usr/bin/bash
1739 1737 1739 12004 cons0 197609 14:01:41 /usr/bin/xinit
1748 1747 1748 6800 pty1 197609 14:01:44 /usr/bin/ps
1746 1745 1746 10316 pty0 197609 14:01:42 /usr/bin/xterm
1747 1746 1747 8820 pty1 197609 14:01:42 /usr/bin/bash
i.e. 2 x bash + 1 x xinit + 1 x XWin + 2 x xterm.
BTW the switch -clipboard is redundant in the proffered line above, its omission
rendering the sequence shorter still.
prev parent reply other threads:[~2020-11-28 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 9:08 Fergus Daly
2020-11-28 14:14 ` Fergus Daly [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=DB6PR03MB3013F3437D4E4667DDC41CC3A4F70@DB6PR03MB3013.eurprd03.prod.outlook.com \
--to=fergusd84@outlook.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).