From: Hugh Wolf <hwolf@deutsches.lieder.de>
Subject: Re: Emacs from CVS question
Date: Sun, 30 Nov 2003 20:30:06 GMT [thread overview]
Message-ID: <irsyb.266544$ao4.928012@attbi_s51> (raw)
In-Reply-To: m2u14n9nhx.fsf@bitstream.net
On 2003-11-29, Tim McNamara <timmcn@bitstream.net> wrote:
> 4. The Xaw3d toolbars are missing from my build of 21.3, but are
> present in the 21.2 build from fink. My impression was that this
> should have been included in the build automagically, but wasn't.
If you look at the fink .info file for whatever 21.2 build you're
running can see what options were used to build it. Look at the value
of ConfigureParameters.
For instance emacs21-xaw3d.info in the unstable tree has this:
ConfigureParams: --with-x --with-x-toolkit=lucid --without-gif \
--infodir='${prefix}/share/info' --mandir='${prefix}/share/man'\
--libexecdir='${prefix}/lib'
The only difference between the xaw3d info and the other x11 emacs
info is that the latter also includes --without-toolkit-scroll-bars.
NB: it's NOT a good idea to build software outside of fink that has
dependencies on fink-provided packages like xaw3d (not impossible but
not a good idea). If you want to install xaw3d via fink, then you
should build your emacs 21.3 with fink. Or, if you really think it's
a good idea to install into /usr/local (I don't), handle all the
non-standard dependencies that way as well, including xaw3d. Don't
mix them.
> 5. The Option key works as META in Carbon but not in X11 (I think
> that may be a problem with XDarwin or OroborOSX, since the Option
> key works as META in Terminal).
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:
clear mod1
keycode 66 = Meta_L
keycode 63 = Mode_switch
add mod1 = Meta_L
This is with the Pro keyboard. The result is that option/alt is my
meta key and command/apple is my alt key in X11.
> 6. The Carbon build is HUGE- 95 MB! Can this be slimmed down?
Mine is 15.6MB for emacs itself -- less than half the size of the X11
build (36.7MB). Where are you seeing 95MB?
next prev parent reply other threads:[~2003-11-30 20:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-29 15:56 Emacs from CVS question Tim McNamara
2003-11-30 6:20 ` Eli Zaretskii
[not found] ` <mailman.805.1070176829.399.help-gnu-emacs@gnu.org>
2003-11-30 6:54 ` Tim McNamara
2003-11-30 7:12 ` Eli Zaretskii
2003-11-30 12:43 ` Glenn Morris
2003-11-30 19:30 ` Tim McNamara
2003-11-30 13:20 ` Piet van Oostrum
2003-11-30 19:32 ` Tim McNamara
2003-11-30 14:54 ` Martin Stemplinger
2003-11-30 19:36 ` Tim McNamara
2003-11-30 20:30 ` Hugh Wolf [this message]
2003-11-30 22:03 ` Tim McNamara
2003-11-30 22:45 ` Hugh Wolf
2003-12-01 1:21 ` Tim McNamara
2003-12-02 0:08 ` Hugh Wolf
2003-12-02 0:39 ` Tim McNamara
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='irsyb.266544$ao4.928012@attbi_s51' \
--to=hwolf@deutsches.lieder.de \
/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).