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: Tue, 26 Oct 2010 13:01:00 -0000 [thread overview]
Message-ID: <4CC6D135.2090606@dronecode.org.uk> (raw)
In-Reply-To: <20101025102521.GA54939@justpickone.org>
On 25/10/2010 11:25, David T-G wrote:
> Hi again, folks --
>
> ...and then David T-G said...
> %
> ...
> % I hate these kinds of errors because it's so incredibly hard to get a
> % real resolution to the problem, but I'll not turn down having my gvim
> % work again :-)
>
> Even that is taken from me now. I had gvim happily open on a file,
> closed it, opened another file, and we're tiny. When I have
>
> set guifont=Courier\ Bold\ 10
>
> in my .vimrc it is at least visible, although still small, and doesn't
> change with the font size, but it does change size if I specify different
> fonts (ie Lucida at any size is wider than Courier or Courier Bold at any
> size, while Times New Roman is very small); when I comment it out I'm back
> to the crazy tiny that I had before.
>
> Any more ideas? :-(
More questions, certainly.
From the examples you have given (xterm works, gvim doesn't), I was assuming
that this meant that core (server-side) fonts are correctly sized, Xft
(client-side) fonts aren't.
But perhaps you mean that gvim is the only application which shows this problem?
You might compare the appearance of the fonts shown by 'xfd -fa Courier' and
'xfd -fn -*-courier-medium-r-*-*-*-120-*-*-*-*-*-*' to test that.
--
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/
next prev parent reply other threads:[~2010-10-26 13:01 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 [this message]
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
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=4CC6D135.2090606@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).