Your message dated Sun, 30 Sep 2007 18:48:57 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#211894: Bitmap fonts
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: vim-gtk
Version: 1:6.2-098+1
Severity: normal
I've just upgraded from the 6.1 packages, and setting
set guifont=7x13
wreaks havoc on the display. The font becomes huge and unreadable.
Trying smaller fonts, like 6x12, result in the same thing. The 7x13 font
works just fine for mxterms, so I know it's still out there, somewhere.
The guifont variable is originally set in my .gvimrc, but setting it in
a running window has the same effect.
Presumably this has something to do with the using GTK2 now?
The help for guifont includes:
:set guifont=Screen15,\ 7x13,font\\,with\\,commas
will make vim try to use the font "Screen15" first, and if it fails it
will try to use "7x13" and then "font,with,commas" instead.
For the GTK+ 2 GUI the font name looks like this: >
:set guifont=Andale\ Mono\ 11
That's all. XLFDs are no longer accepted.
[...]
If an empty font list is given, vim will try using other resource
settings (for X, it will use the Vim.font resource), and finally it
will try some builtin default which should always be there ("7x13" in
the case of X).
I don't know what "XFLDs" are -- and using an uncommon acronym like that
is a bug in itself -- but clearly '7x13' should still work.
Are there other settings I can report, other info I can give?
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux fenric 2.4.20-fenric4 #1 SMP Wed Aug 6 04:16:27 EDT 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages vim-gtk depends on:
ii dpkg 1.10.13 Package maintenance system for Deb
ii libatk1.0-0 1.2.4-1 The ATK accessibility toolkit
ii libc6 2.3.2-7 GNU C Library: Shared libraries an
ii libglib2.0-0 2.2.3-1 The GLib library of C routines
ii libgpmg1 1.19.6-12.1 General Purpose Mouse Library [lib
ii libgtk2.0-0 2.2.4-1 The GTK+ graphical user interface
ii libncurses5 5.3.20030719-2 Shared libraries for terminal hand
ii libpango1.0-0 1.2.5-1 Layout and rendering of internatio
ii libperl5.8 5.8.0-21 Shared Perl library.
ii libruby1.8 1.8.0-2 Libraries necessary to run the Rub
ii python2.3 2.3-4 An interactive high-level object-o
ii tcl8.3 8.3.5-4 Tcl (the Tool Command Language) v8
ii vim 1:6.2-098+1 Vi IMproved - enhanced vi editor
ii xlibs 4.2.1-11 X Window System client libraries
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Sep 29, 2003 at 06:44:40PM +0200, Thomas Nilsson wrote:
> Stumbled over this report while looking for clues about another bug. This
> is what I did to reenable bitmap fonts in GVim.
>
> In ~/.fonts.conf or /etc/fonts/local.conf place this within the
> <fontconfig> tag:
>
> <!-- Enable Bitmap fonts -->
> <dir>/usr/X11R6/lib/X11/fonts</dir>
>
> That should enable bitmap fonts for your GTK+2 applications. If you're
> using fontconfig that is. No idea how to do it otherwise (if it's even
> possible to have gtk+2 without it.)
As noted above, this appears to have been a configuration issue with
GTK2 and not a problem specific to Vim. Since there's a noted way to
fix it, I'm closing this bug.
James
--
GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
--- End Message ---
