[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: font handling broken in cvs emacs --with-ns (MacOS X)

From: Peter Dyballa
Subject: Re: font handling broken in cvs emacs --with-ns (MacOS X)
Date: Mon, 5 Jan 2009 00:28:38 +0100

Am 04.01.2009 um 23:22 schrieb B Smith-Mannschott:

Documentation clearly states that after an update you need to do a 'make
bootstrap' unless you wish to have a GNU mess.

   make install

I do it this way because it works.

If your way would work, then you would not need to consider writing a bug report ...

And I don't need the build to be fast.

A bootstrap built build is not faster – it just has up-to-date ELC files.

It would be different if I were hacking on emacs myself because
the long edit-compile-run cycle would be terrible.

There are experienced GNU Emacs developers who take that burden from you! And this makes the difference: you're not using the stable GNU Emacs 22.3 (also in Carbon available) but the not yet released GNU Emacs 23.0.60 *from CVS*. And therefore building it needs 'make bootstrap.'

I found the reference to make bootstrap in INSTALL.CVS (thanks grep).
I had been reading INSTALL, which doesn't breathe a word of it.
Scrubbing the source directory seems to force a make bootstrap, which
is good. If I find I need emacs to build faster, then I'll look into
INSTALL.CVS more carefully.

You're mixing up a few things! In a regular and stable GNU Emacs release you won't see the INSTALL.CVS file. Does this help?

You don't need that Carbon stuff! Just choose from the Options menu "Set
Default Font…"! Isn't it clearly documented?

I may have missed it among emacs' *1.9 million words* of documentation. ;-)

Well, maybe you came too late to, because some weeks ago it has lost from the Help menu an entry to read the part on Right now you can easily find in the Emacs node one on

        * Mac OS / GNUstep::    Using Emacs under Mac OS and GNUstep.

Is all that gets written. still, it's obviously storing the setting
somewhere, because the change I made is maintained across restarts of


Fascinating. I see a lot of other stuff here too. settings for
org-mode, for example. Does write all customizations here
instead of custom.el?

I don't think so. Only its "options" are saved in this XML file. (The defaults command or Property List Editor also work on this file.)

How will that jive with my attempts to keep a
single emacs configuration (in version control) across my Mac and
Linux machines?

Well, I make most of my changes into a *system* of init files. From ~/.emacs particular init and customisation files are read, mostly depending on emacs-major-number and window-system.



What is this talk of 'release?' Klingons do not make software 'releases.' Our software 'escapes,' leaving a bloody trail of designers and quality assurance people in its wake.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]