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
Date: Mon, 27 Sep 2010 15:05:00 -0000	[thread overview]
Message-ID: <4CA0B2D2.8050203@dronecode.org.uk> (raw)
In-Reply-To: <20100922153425.GG26157@justpickone.org>

On 22/09/2010 16:34, David T-G wrote:
> Hi, all --
>
> [Let's see if I can provide all of the details the first time instead of
> having to go back and forth just for foundation... :-]

Can you attach your /var/log/XWin.0.log, please?

> I have used Cygwin for years and have been using the cygwin gvim (versus
> the Windows-native vim + gvim) for some time now.  I had occasion to do a
> fresh install of 1.7.7 on a freshly-rebuilt laptop after a hard drive
> crash and so I don't think that I have any of the upgrade gotchas biting
> me, but stranger things have happened :-)
>
> When I first started gvim after my install, the font was invisibly tiny
> both for the content and for the menus.  [Note that both xterm and rxvt-X
> are fine.]  Using another computer to see where I was going and matching
> the keystrokes I attempted to set the font to "Lucida Console 12" but
> found no change.  I have manually (a bummer, but I gather from the FAQs
> that the lack of dependency linking is temporary) added the font-bh-dpi75
> and font-bh-lucidatypewriter-dpi75 packages with no effect.  I have set
> the guifont variable in my .vimrc file, and the tiny window was somewhat
> differently sized but still tiny.  Finally, I have of course googled for
> "cygwin +gvim +font (size or tiny)" and similar to see what others have
> found, but I haven't matched anything more useful than the guifont
> setting.
>
> What do I need to fix and where to make my gvim readable?

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


  parent reply	other threads:[~2010-09-27 15:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 15:34 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 [this message]
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
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=4CA0B2D2.8050203@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).