unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: Too small fonts after Emacs-Snapshot update
Date: Wed, 27 Feb 2008 18:35:58 +1100	[thread overview]
Message-ID: <87k5kq4zs1.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.7949.1204019436.18990.help-gnu-emacs@gnu.org

Peter Dyballa <Peter_Dyballa@Web.DE> writes:

> Am 26.02.2008 um 09:30 schrieb Tim X:
>
>> I suspect it could be some bit of 'kruft' left over from a dist upgrade.
>
>
> LibXft can be a problem – this is true in Mac OS X 10.4 (Tiger): libXft is
> obviously too old here.
>
> Recent GNU Emacs 23.0.60 is able to use more than one font backend: X11,
> Freetype, Xft:
>
> 	!Emacs.FontBackend:	x
> 	!Emacs.FontBackend:	xft
> 	!Emacs.FontBackend:	ftx
>
> Since some days you can combine backends:
>
> 	Emacs.FontBackend:	x,xft
>
> There can also be another source of problems: libfontconfig. It has to be
> modern, too, to allow to select fonts by certain properties.
>

thanks Pete. Actually, my problems now appear to be hardware
based. Looks like I've developed some bad memory in my system. However,
the stuff you provided on specifying the font backend is very
interesting and I will be experimenting to see what, if any,
differences I get.

Tim
>

-- 
tcross (at) rapttech dot com dot au


  parent reply	other threads:[~2008-02-27  7:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24 20:18 Too small fonts after Emacs-Snapshot update Sven Bretfeld
2008-02-24 20:44 ` Thierry Volpiatto
2008-02-24 20:49   ` Sven Bretfeld
2008-02-24 21:10     ` Thierry Volpiatto
2008-02-24 22:34       ` Sven Bretfeld
2008-02-25 12:39       ` Sven Bretfeld
2008-02-25 13:19         ` Peter Dyballa
2008-02-25 13:48           ` Sven Bretfeld
2008-02-25 13:52             ` Bastien
     [not found]       ` <mailman.7903.1203943187.18990.help-gnu-emacs@gnu.org>
2008-02-25 18:22         ` Romain Francoise
     [not found]         ` <mailman.7941.1203989923.18990.help-gnu-emacs@gnu.org>
2008-02-26  8:30           ` Tim X
2008-02-26  9:50             ` Peter Dyballa
2008-02-26 14:59             ` Romain Francoise
2008-02-27  7:38               ` Tim X
     [not found]             ` <mailman.7949.1204019436.18990.help-gnu-emacs@gnu.org>
2008-02-27  7:35               ` Tim X [this message]
     [not found]   ` <mailman.7866.1203886166.18990.help-gnu-emacs@gnu.org>
2008-02-25  6:38     ` Tim X
     [not found] ` <FB31DE45-543C-47D2-BDD2-FAD4BE6C1FED@Web.DE>
2008-02-24 20:58   ` Sven Bretfeld
     [not found]     ` <37312008-B32F-4CCB-8A8E-23CEAC0FC882@Web.DE>
2008-02-24 22:47       ` Sven Bretfeld
2008-02-25  0:26         ` Peter Dyballa
     [not found] <mailman.7863.1203884313.18990.help-gnu-emacs@gnu.org>
2008-03-03 22:01 ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k5kq4zs1.fsf@lion.rapttech.com.au \
    --to=timx@nospam.dev.null \
    --cc=help-gnu-emacs@gnu.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).