Re: Emacs from CVS question

[Tim McNamara]

Hugh Wolf <hwolf@deutsches.lieder.de> writes:

> On 2003-11-30, Tim McNamara <timmcn@bitstream.net> wrote:
>
>> Not mixing fink-built and non-fink-built dependencies makes sense.
>> Thus far 21.3 doesn't seem to be available via fink
>
> Time to make your own .info file :) It's very easy in this case,
> since you can copy one that's there already and modify it as needed.
> Put it in the local tree, so fink knows it's not part of its
> distribution.
>
>> (and in any event the Carbon build would not be available via fink
>
> Right, but this is completely standalone, it doesn't depend on
> anything at all other than what comes with the osx developer tools
> -- not on fink and not on anything else you might happen to have in
> /usr/local.

OK, that was over my head.  ;-)

>>> I haven't used XDarwin.app in a long time now, but this sounds
>>> like an .Xmodmap thing.  With X11.app my ~/.Xmodmap looks like
>>> this:
>>
>> Huh.  I don't have an ~/.Xmodmap file... 
>
> If you want option to be meta, you need one.  The standard osx X11
> key mapping makes command/apple act as meta and option/alt act as
> alt.

Even if my .emacs contains (setq mac-command-key-is-meta nil)?  Now,
in Terminal Option = Meta as there's a check box in Preferences for
this, but it doesn't carry over to X11 obviously.  And in the Carbon
version Option = Meta, so for the sake of consistency it'd be nice to
have the same functionality in the X11 version.  I'll look into using
an .Xmodmap file to set this.

>>> Mine is 15.6MB for emacs itself -- less than half the size of the
>>> X11 build (36.7MB).  Where are you seeing 95MB?
>>
>> Get Info on Emacs.app = 96.6 MB. 
>
> Right, ok, but that's with all the lisp and info files etc.  You'll
> see exactly the same thing with the X11 build, except those parts
> will be under /usr/local.
>
>> Oddly enough, neither the Carbon version nor the X11 version I
>> compiled can find the info files
>
> This works ok for me.

Which is what makes me wonder if I miscued the build process in some
way, missed a library that I'm supposed to have, etc..  I haven't
heard anything about this being a problem for other people building
from the CVS snapshot.

>> which are at the place that "make install" put them
>
> If you leave them wherever the install step puts them, it should
> work.  With the carbon emacs you should also be able to copy them
> into the application bundle (as you've apparently done).  I don't do
> this myself, but I did try it once, some time ago, and it seemed to
> work fine.

I didn't do anything with where anything was installed.  My
interaction with the compiling process amounted to:

(Using Andrew Choi's script for obtaining Emacs from CVS at Savannah;
then gunzipping/untar'ing the file, then cd'ing to the emacs source
directory where I invoked:)

./configure --with-carbon --without-x
make bootstrap
sudo make install

I invoked 'make distclean' after getting a working version for Carbon,
and then I decided to build a copy for X11 use:

./configure --with-x --without-carbon
make bootstrap
make install

> What symptom are you seeing -- 'meta-x info' shows nothing?

'M-x info' produces the Gnus info tree as the top level, but no other
info.  Using the menu bar Help item produces either nothing (e.g.,
selecting "About Emacs" with the mouse results in "menu-bar help-menu
about" in the minibuffer but no help screen; selecting "Read the Emacs
manual" results in "info file emacs does not exist" in the minibuffer
and a blank buffer frame named "info."

It's kind of interesting to me that *both* builds have the same
behavior in this regard.  Is there some way to check where Emacs
*thinks* the info files are?  Is it looking somewhere other than
/usr/local/info?