After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 81555 - Cannot enter font name manually.
Cannot enter font name manually.
Status: RESOLVED DUPLICATE of bug 81900
Product: gnome-terminal
Classification: Core
Component: general
1.9.x
Other All
: Normal normal
: future
Assigned To: Havoc Pennington
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-05-12 15:29 UTC by Ville Pätsi
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Description Ville Pätsi 2002-05-12 15:29:26 UTC 
I have fonts that don't have a family name or any other info, they only
have a name. In 1.4 you could use these bitmap fonts in gnome-terminal by
typing the name in the font field in preferences. Now you can't.
Comment 1 Havoc Pennington 2002-05-13 00:12:16 UTC 
Taking off GNOME2.0.0 because it breaks UI freeze, and I don't have
time to do it by tomorrow's deadline. You could always use
gconftool... /me runs

The current font picker is basically a hack until we have a terminal
widget that can use the Pango font selector, VTE will give us that, or
maybe someone will figure out how to make Zvt use it.
Comment 2 Luis Villa 2002-05-13 00:22:56 UTC 
Eck. I need to make sure people aren't setting 2.0.0 just for the heck
of it, don't I...
Comment 3 Ville Pätsi 2002-05-13 05:23:47 UTC 
Except changing it from gconf-editor didn't work. I set the xfont
value to  the font name, but the term just used the first font in the
terminal's font selector, even though the gconf value was something
different.
Comment 4 Havoc Pennington 2002-05-13 05:40:02 UTC 
Setting it from gconf-editor probably works as long as you never open
the profile editor... ;-)

This is a fairly bad bug and indicates that the font selector is
fundamentally hosed, I just don't know how to fix it... the font
selector also has issues with handling encodings correctly.
Comment 5 Havoc Pennington 2002-09-22 20:13:43 UTC 

*** This bug has been marked as a duplicate of 81900 ***