X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:reply-to:subject:references:to:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=XRiqPdOIDVnEMk3s zeYjuOb1wVMkMdFecENhL7y3I+PeUlV7S3WlOsLIF2SpL6AOceiGPxWMsnqmUjlR d4LFZFM7GS0pQQQ3lZLLSdnS2GN1NsKkjUvC3VJGL35uWqApXH42jLQgkh71bW6I VFhZ47KCE6gg9DNv8lppquZKo+A= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:reply-to:subject:references:to:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=FKEY1+9ZGW9clUGQP7taOa CoaCU=; b=SvTJvgUyT/emh7PIsUB9MmhzAPRNjexFVvgzNcpCmjXEkqHOa8CNLG gGKpKzBkgDNC3a2fev1/FK5U0g0qV21GOzUNF+iCFPsArjJribhd9tXEhgtuMZ2s mDe05m5JGHn9Q08gb05zCO+27RoIIY7NwSuTE+6QMm8eIxvpR656s= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.3 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=Book, recall, oriented, Hx-languages-length:2501 X-HELO: csmail.cs.umass.edu Reply-To: moss AT cs DOT umass DOT edu Subject: Re: cygwinX xwin resolution References: <87424135-6f1e-9b52-8a56-c79159d910d7 AT utoronto DOT ca> To: cygwin AT cygwin DOT com From: Eliot Moss Message-ID: <8d89912b-14e5-3908-8d4e-ae60fb29e56c@cs.umass.edu> Date: Fri, 22 Jul 2016 09:32:47 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <87424135-6f1e-9b52-8a56-c79159d910d7@utoronto.ca> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 7/22/2016 12:23 AM, Dr. Rob Higgins wrote: > I cannot find, after two days, any documentation on how and where to specify resolution parameters. > I must be barking up the wrong trees. > > My laptop under Windows has recommended resolution set at 3200 x 1800 > > CygwinX X Windows are much to small, and barely readable. > > Can anyone just tell me where to look, or what to specify? As I recall, X does not have a strong notion of "resolution". It does know the dimensions of the *screen* measured in pixels. One specifies window sizes also in pixels. I noticed similar effects when I moved to a Microsoft Surface Book, which has 3000 x 2000 pixels on the screen. Perhaps the most relevant file is your .Xdefaults. For character- oriented applications such as xterm and emacs, windows sizes are generally expressed in terms of lines and columns. I found I needed to specify larger *fonts*, e.g.: XTerm*font: -adobe-courier-medium-r-normal-*-34-240-*-*-*-*-*-* XTerm*bodyFont: -adobe-courier-medium-r-normal-*-34-240-*-*-*-*-*-* Emacs.default.attributeFont: -adobe-courier-medium-r-normal-*-34-240-*-*-*-*-*-* Xpdf*fontList: -*-helvetica-medium-r-*--*-240-*-*-*-*-iso8859-1 (The last one took some finding!) For applications that measure in terms of pixels, I needed to specify larger values, e.g.: Xpdf*geometry: 3000x1875+0+0 (In this last one, 1875 leaves room for the icons in the bar at the bottom under Windows 10.) The xrdb program can be helpful around all this. In particular, xrdb -symbols will output symbol definitions that you can feed into the C preprocessor (cpp) to process a file with symbolic names such as WIDTH and HEIGHT. You can also undoubtedly capture and process these with a bash script, or a script in a variety of scripting languages, to help set up the values you want when creating windows. Now, backing off a little from my more absolute statement at the beginning, xrdb -symbols *does* print out X_RESOLUTION and Y_RESOLUTION. These give the number of pixels per meter on the screen. For my Surface Book their value is 7576. Presumably you could capture that and figure something out. And presumably applications could as well, but I am not aware of applications that auto-adjust according to the screen resolution. The main ones I use do not seem to take it into account. (And many Windows apps do not seem to either. I get tiny icons sometimes (Eclipse) or cut Windows areas (CrashPlan), etc.) Hope this help! Eliot Moss -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple