From: Andrew Choi <akochoi@shaw.ca>
Cc: emacs-devel@gnu.org
Subject: Emacs for Mac OS X
Date: Sun, 14 Apr 2002 20:28:31 -0600 [thread overview]
Message-ID: <m2r8lhlmpc.fsf@shaw.ca> (raw)
Hi Richard,
Sorry it took such a long time. After much testing and catching up
with changes that have been made, I now have a patch with respect to
the latest CVS version of Emacs that will allow it to run quite stably
on Mac OS X. It supports most of version 21's features except images.
The patch consists of small changes to many source files. These
should be safe because they are conditioned on the MAC_OS, MAC_OS8, or
MAC_OSX macros.
There are also small changes to configure.in, make-dist,
src/Makefile.in to allow the configuration and build process to work.
Change logs are updated. The mac/README and mac/INSTALL files are
updated. The Mac OS section of the manual is also updated.
The biggest change involves removing the files mac/src/mac.c,
mac/src/macfns.c, mac/src/macmenu.c, mac/src/macterm.c,
mac/inc/macgui.h, and mac/inc/macterm.h, and placing new versions of
these files in src.
A new directory mac/Emacs.app is added. Three new files
src/unexmacosx.c, src/m/powermac.h, and src/s/darwin.h are added.
The entire patch is written by me. A few changes are due to Tsutomu
Ikegami. We have both filed assignment papers with FSF.
The patch and the new files can be found at:
http://homepage.mac.com/akochoi/FileSharing2.html
I have write access to the CVS and can also check in this patch.
Would you like me to do this? Also, should I add it to the head
branch?
Andrew.
next reply other threads:[~2002-04-15 2:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 2:28 Andrew Choi [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-27 1:28 Emacs for Mac OS X Andrew Choi
2003-05-03 17:33 Mary Bamford
2003-05-07 9:55 ` Andreas Schwab
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2r8lhlmpc.fsf@shaw.ca \
--to=akochoi@shaw.ca \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.