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 B00A33858400 for ; Sun, 24 Oct 2021 11:20:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B00A33858400 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=cs.umass.edu Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=cs.umass.edu Received: from [192.168.1.118] (canterbury.free-online.co.uk [195.166.150.114]) by mailsrv.cs.umass.edu (Postfix) with ESMTPSA id 1DDD4401AF48; Sun, 24 Oct 2021 07:20:14 -0400 (EDT) Reply-To: moss@cs.umass.edu Subject: Re: Confusing Cygwin X / xlaunch issue From: Eliot Moss To: cygwin References: <1e4edecf-166c-e3c1-f961-b31bfa01271f@cs.umass.edu> Message-ID: <207b69da-7eed-df9c-6e92-feabd552c00b@cs.umass.edu> Date: Sun, 24 Oct 2021 12:20:15 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 MIME-Version: 1.0 In-Reply-To: <1e4edecf-166c-e3c1-f961-b31bfa01271f@cs.umass.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, NICE_REPLY_A, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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: Sun, 24 Oct 2021 11:20:15 -0000 A follow up: I have tried other combination of which display is main when booting and which is main when starting X. These seem to be the case: - Getting xterm fonts the right size requires *booting* with the hi-res display being main. X can be starting with either being main. - Getting the menu to come up requires starting X with the hi-res display being main; I can then change which display is main after I have started X. So the only way I can get my preferred behavior seems to be: - Boot with the hi-res screen as main - Start X - Switch to have the lo-res screen as main (which requires switching back before any reboot ...) Does this all fit the understanding of how XWin starts up and interacts with Windows display settings? Best wishes - Eliot Moss