From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailsrv.cs.umass.edu (mailsrv.cs.umass.edu [128.119.240.136]) by sourceware.org (Postfix) with ESMTPS id BE9573857C65 for ; Tue, 29 Sep 2020 12:26:59 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org BE9573857C65 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=cs.umass.edu Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=moss@cs.umass.edu Received: from [192.168.0.16] (c-24-62-203-86.hsd1.ma.comcast.net [24.62.203.86]) by mailsrv.cs.umass.edu (Postfix) with ESMTPSA id 699DE4023B8A; Tue, 29 Sep 2020 08:26:59 -0400 (EDT) Reply-To: moss@cs.umass.edu Subject: Re: Cygwin/X11 on Windows 10 To: Cygwin References: From: Eliot Moss Message-ID: <2c7d0361-b78c-f2e9-01d6-17fc879c5c91@cs.umass.edu> Date: Tue, 29 Sep 2020 08:27:00 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_NUMSUBJECT, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, 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 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Sep 2020 12:27:01 -0000 On 9/29/2020 6:26 AM, Thomas Schweikle via Cygwin wrote: > Hi! > > I've managed to install cygwin/X on Windows 10. Now I'm looking for command > "startxwin" -- does not seen to exist. If following instructions from > https://x.cygwin.com/docs/ug/setup.html it should be installed? Or is an > extra package selected needed beyond what is given in upper mentioned > handbook online? > > If I start "XWin.exe -multiwindow" directly it starts and finishes > immediately. The recommended idea of creating an > executable "~/.startxwinrc" holding only "exec sleep infinity" does not > help. Same behaviour as before. Any other suggestions? startxwin is in the xinit package. Personally I use xlaunch, in the xlaunch package. xlaunch with no arguments fires up a GUI where you can configure it and save an xlaunch file, e.g., ~/config.xlaunch. I put a link to xlaunch in my Windows task bar, with the follow command line it: C:\cygwin64\bin\run.exe /bin/xlaunch -p /usr/bin -run /home/moss/config.xlaunch You'll need to change paths for your file locations, of course. It uses startxwin. Below is my personal .startxwinrc file for a sample. It starts a couple of xterm windows and an emacs, all iconized. The emacs geometry suits my high resolution screen. The "wait" is important - otherwise things exit immediately and the X server terminates. #!/bin/bash xrdb -merge ${HOME}/.Xdefaults xmodmap ${HOME}/.Xmodmap UC="${USER} console" xterm +tb -geometry 110x62+4+0 -T "${USER}" -n "${USER}" -name "${USER}" -bg rgbi:.0/.2/.2 -ls -iconic & xterm +tb -geometry 110x62-10+0 -T "${UC}" -n "${UC}" -name "${UC}" -bg rgbi:.5/.0/.1 -ls -iconic & emacs --chdir=${HOME} --no-splash --iconic --geometry=130x60+100+100 -T emacs & wait