From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: Too small fonts after Emacs-Snapshot update
Date: Tue, 26 Feb 2008 19:30:27 +1100 [thread overview]
Message-ID: <87oda43ysc.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.7941.1203989923.18990.help-gnu-emacs@gnu.org
Romain Francoise <romain@orebokech.com> writes:
> Sven Bretfeld <sven.bretfeld@gmx.ch> writes:
>
>> I've now downgraded my Emacs version to 23.0.50 again. I think I
>> will be happier with this one.
>
> Or you could keep the latest snapshot and use --disable-font-backend,
> I guess.
>
>
I've found that even if you have built emacs with --enable-font-backend,
you can still use the normal fonts. I wasn't even aware that (for
example) your emacs-snapshot was being built with --enable-font-backend
and had just left my .Xresources Emacs.font: as it always has been - no
issues and no observable difference from earlier versions of either
emacs-snapshot or running emacs22.
I am currently dealing with a very odd problem though. I have two
machines, both running Debian. One one machine (this one) both
emacs-snapshot and an emacs I've built myself from CVS are working
fine. No issues.
However, on the other machine I get weird errors about void function
definitions, signal 11 segfaults, and other 'weirdness' in both the
latest emacs-snapshot and emacs built from CVS. The only real difference
between the two machines is that the one I'm having problems with has
been running Debian since 2001, upgrading from (I think)
potato/woody. The other machine was a fresh Debian install about 12
months ago. I suspect it could be some bit of 'kruft' left over from a
dist upgrade. Frustrating because its my work machine and I've not got
time to chase down the problme just now. Had to revert back to emacs22
until I get time to sort things out.
Tim
--
tcross (at) rapttech dot com dot au
next prev parent reply other threads:[~2008-02-26 8:30 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 [this message]
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
[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=87oda43ysc.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).