From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: Tragedy
Date: Wed, 08 Oct 2008 17:33:23 +1100 [thread overview]
Message-ID: <874p3noato.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: ff18d685-64db-4de0-a957-8e64192b2734@b38g2000prf.googlegroups.com
rustom <rustompmody@gmail.com> writes:
> On Oct 7, 12:35 pm, Tim X <t...@nospam.dev.null> wrote:
>> May or may not be of use, but I encountered the same problem after
>> updating CVS emacs last Thursday. The solution I found that works under
>> X is to add
>>
>> Emacs.FontBackend: xft
>>
>> to my .Xresources file.
>>
>> Tim
>>
>> --
>> tcross (at) rapttech dot com dot au
>
> Hi Tim
> Can you explain a little what that does?
> A little context for asking:
> 1. Ive been running emacs (21 and 22) for a while under debian etch
> and ubuntu dapper. Some of the settings of background color etc are
> set in Xresources. And every once in a while -- quite randomly -- it
> does not work.
>
> 2. Recently upgraded the dapper to hardy. Now 'snapshot' is not 22 but
> 23. Supposedly the font support is better there but in fact it looks
> distinctly worse.
>
> 3. When upgrading from dapper to hardy the upgrade broke on xfonts-
> scalable. A little googling told me the problem is evidently in
> xfonts-utils. Trying to set that up broke everything and I had to
> give up upgrading and go for a new install.
>
Current emacs cvs (aka emacs 23) has support for True Type and anti-aliased fonts and
specifying of fonts using the fontconfig or gtk font naming style. It
can also support otf and m17n for complex fonts needing more advanced
rendering support.
The line
Emacs.FontBackend: xft
tells emacs to use libxft for font rendering. this will give
anti-aliased fonts etc. So now, I can specify my font like
emacs -fn "DejaVu Sans Mono-12"
If you are finding your not getting good fonts, then its likely that
either you need to select a better font or you need to install some of
the True Type fonts e.g. font packages starting with ttf-
The xfonts-* packages are not TrueType fonts - they are the older X
windows fonts and on the whole, are not as nice looking as the TT
fonts.
You should look at the News file that comes with the emacs-snapshot
package - all of this is outlined there and often has pointers to more
information.
HTH
Tim
--
tcross (at) rapttech dot com dot au
next prev parent reply other threads:[~2008-10-08 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.379.1223308471.25473.help-gnu-emacs@gnu.org>
2008-10-07 0:01 ` Tragedy Memnon Anon
2008-10-07 7:35 ` Tragedy Tim X
2008-10-07 7:55 ` Tragedy rustom
2008-10-08 6:33 ` Tim X [this message]
2008-10-06 15:55 Tragedy Adolfo De Unanue
2008-10-06 16:47 ` Tragedy Lennart Borgman (gmail)
2008-10-06 17:30 ` Tragedy Peter Dyballa
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=874p3noato.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).