public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: d10@justpickone.org
Subject: Re: gvim tiny font in 1.7.7 (back again)
Date: Thu, 28 Oct 2010 16:57:00 -0000	[thread overview]
Message-ID: <4CC9AB8A.4020102@dronecode.org.uk> (raw)
In-Reply-To: <20101028014122.GP26157@justpickone.org>

On 28/10/2010 02:41, David T-G wrote:
> Jon, et al --
>
> ...and then Jon TURNEY said...
> %
> % On 25/10/2010 11:25, David T-G wrote:
> %>
> ...
> %>Any more ideas? :-(
> %
> ...
> % But perhaps you mean that gvim is the only application which shows this
> % problem?
>
> Yup -- so far, anyway.
>
>
> %
> % You might compare the appearance of the fonts shown by 'xfd -fa Courier'
> % and 'xfd -fn -*-courier-medium-r-*-*-*-120-*-*-*-*-*-*' to test that.
>
> I'm back with xfd loaded now.  Sure enough, the two are distinctly
> different; the former is smaller than the latter, although not so tiny as
> to be invisible as in gvim.  This sure sounds like a lead, though!
>
> I am leery of posting attachments to the mailing list, so I haven't
> attached screen shots of the xfd layouts.  In addition, I ran xlsfonts
> and it generated 2582 lines; that's probably more than I should paste
> here.  Let me know what information I can provide, however.
>
> Soooo...  What do I do to make my fonts all be happy?

The fonts aren't supposed to be visually identical, as they are potentially 
different fonts being draw by different renderers.  But the sizes should be 
approximately the same.

Let me try asking the question a different way: Does 'xfd -fa 
"Courier-10:style=Bold"' show a reasonably sized font at the same time as 
gvim, with that font set, doesn't? (In which case one might conclude this is 
probably a gvim bug)

I don't think this is quite the same problem as reported by Frédéric Bron, as 
you don't seem to be using -resize.

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2010-10-28 16:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 15:34 gvim tiny font in 1.7.7 David T-G
2010-09-25 18:25 ` Frédéric Bron
2010-09-27  0:51 ` David T-G
2010-09-27 15:05 ` Jon TURNEY
2010-10-01 10:23   ` David T-G
2010-10-06 14:08     ` Jon TURNEY
2010-10-08 11:32       ` David T-G
2010-10-23 10:17         ` David T-G
2010-10-25 10:25           ` gvim tiny font in 1.7.7 (back again) David T-G
2010-10-26 13:01             ` Jon TURNEY
2010-10-27 11:30               ` David T-G
2010-10-28  0:53               ` Frédéric Bron
2010-10-28  1:43                 ` David T-G
2010-10-28 16:47                 ` Jon TURNEY
2010-10-28  1:41               ` David T-G
2010-10-28 16:57                 ` Jon TURNEY [this message]
2010-10-28 17:31                   ` David T-G
2010-10-26  4:15           ` gvim tiny font in 1.7.7 Frédéric Bron

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=4CC9AB8A.4020102@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    --cc=d10@justpickone.org \
    /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).