public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: jeff.buckles-cygwin@bookloaf.net
Subject: Re: git gui menu fonts are too small, unreadable
Date: Mon, 20 Jun 2016 12:59:00 -0000	[thread overview]
Message-ID: <9326cdc3-e226-c676-8ef0-8f7518ed90da@dronecode.org.uk> (raw)
In-Reply-To: <b80c6b69-a080-0357-111f-5a82eb2f4c43@bookloaf.net>

On 07/06/2016 23:31, Jeff Buckles wrote:
> Menu fonts in 'git gui' are too small to be readable
> (only one or two pixels high).   "gitk" works fine.

Thanks for reporting this problem.

I was able to reproduce this problem, with a fresh installation, but 
only on x86, not on x86_64

It seems that default font used by git gui is '0pt DejaVu Sans', where 
0pt has a special meaning in Tcl/Tk of 'a platform-dependent default 
size' [1], which is 12 pt for on X11.

There seems to be a bug somewhere in Tcl/Tk (or perhaps in the 'git gui' 
script), so that on x86, the size attribute it ends asking fontconfig 
for is INT_MIN, not 0.

It also seems that fontconfig has recently changed it the way it handles 
this invalid value, now giving you a very tiny font.

Until we have a solution, you can work around this by setting the font 
to have a definite size in ~/.gitconfig, e.g. adding

> [gui]
>         fontui = -family \"DejaVu Sans\" -size 12 -weight normal -slant roman -underline 0 -overstrike 0

[1] https://www.tcl.tk/man/tcl8.5/TkCmd/font.htm#M26

-- 
Jon Turney
Volunteer Cygwin/X X Server maintainer

--
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

      reply	other threads:[~2016-06-20 12:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07 22:32 Jeff Buckles
2016-06-20 12:59 ` Jon Turney [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=9326cdc3-e226-c676-8ef0-8f7518ed90da@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=jeff.buckles-cygwin@bookloaf.net \
    /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).