delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-Original-To: | cygwin AT cygwin DOT com |
Delivered-To: | cygwin AT cygwin DOT com |
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 |
Subject: | Re: Confusing Cygwin X / xlaunch issue |
From: | Eliot Moss <moss AT cs DOT umass DOT edu> |
To: | cygwin <cygwin AT cygwin DOT com> |
References: | <1e4edecf-166c-e3c1-f961-b31bfa01271f AT cs DOT umass DOT 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> |
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 AT cygwin DOT com |
X-Mailman-Version: | 2.1.29 |
List-Id: | General Cygwin discussions and problem reports <cygwin.cygwin.com> |
List-Unsubscribe: | <https://cygwin.com/mailman/options/cygwin>, |
<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe> | |
List-Archive: | <https://cygwin.com/pipermail/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-request AT cygwin DOT com?subject=help> |
List-Subscribe: | <https://cygwin.com/mailman/listinfo/cygwin>, |
<mailto:cygwin-request AT cygwin DOT com?subject=subscribe> | |
Reply-To: | moss AT cs DOT umass DOT edu |
Errors-To: | cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com |
Sender: | "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com> |
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 -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |