Mercurial > emacs
view mac/README @ 68127:40429cab94e1
* mh-index.el (mh-index-search): Checking mh-find-path-run is
unnecessary.
* mh-init.el (mh-sys-path): Co-locate with mh-variants, which uses it.
(mh-variants): Note variable isn't meant to be accessed directly; use
function mh-variants instead.
(mh-variant-info, mh-variant-mh-info, mh-variant-mu-mh-info)
(mh-variant-nmh-info): Co-locate next to mh-variants, which uses them.
Updated to use mh-file-command-p which is more accurrate than
file-executable-p which returns t for directories.
(mh-file-command-p): Move here from mh-utils, since mh-variant-*-info
are the only functions to use it.
(mh-variant-set, mh-variant-set-variant, mh-variant-p): Use function
mh-variants instead of variable. More robust.
(mh-find-path-run): Move here from mh-utils.el. Mention that checking
this variable is unnecessary.
(mh-find-path): Move here from mh-utils.el. With the advent of MH
variants and an mhparam command that doesn't work if there isn't an MH
profile, we can't get libdir for running install-mh. So don't bother.
If there's an issue with the environment, direct the user to install
MH and run install-mh (closes SF #835192). Don't read ~/.mh_profile
directly. Use mh-profile-component which uses mhparam (closes SF
#1016027).
* mh-utils.el (mh-get-profile-field): Rename to
mh-profile-component-value. Add colon to search removing unnecessary
addition of colon to field in mh-profile-component.
(mh-profile-component): Modify call to mh-profile-component-value
accordingly. Move next to mh-profile-component-value.
(mh-find-path-run, mh-find-path, mh-file-command-p): Move to
mh-init.el. It makes sense that code that is only run once per session
(more or less) is in mh-init.el rather than cluttering mh-utils.el.
(mh-no-install, mh-install): Delete.
author | Bill Wohler <wohler@newt.com> |
---|---|
date | Tue, 10 Jan 2006 23:55:42 +0000 |
parents | ae5c2b812667 |
children | 067115a6e738 |
line wrap: on
line source
Emacs for Mac OS Classic and Mac OS X Copyright (C) 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc. Permission is granted to anyone to make or distribute verbatim copies of this document as received, in any medium, provided that the copyright notice and permission notice are preserved, and that the distributor grants the recipient permission for further redistribution as permitted by this notice. Permission is granted to distribute modified versions of this document, or of portions of it, under the above conditions, provided also that they carry prominent notices stating who last changed them. This directory contains the files needed to build Emacs on the Mac OS Classic and Mac OS X. Many of the major features of the Unix version are supported: multiple frames, colors, scroll bars, menu bars, use of the mouse, fontsets, international characters, input methods, and coding systems. Mac OS specific support includes document drag-and-drop in the Finder, transfer of text to and from other applications via the clipboard, and sending AppleScript commands to other applications from Emacs. The following are not supported on Mac OS Classic: unexec (dump-emacs), asynchronous subprocesses (start-process), and networking (open-network-stream). These features work fine on Mac OS X. There is basic support for synchronous subprocesses (call-process) on Mac OS Classic (non-Carbon build only) although Unix commands that are used will need to be ported. FIXME: Metrowerks CodeWarrior Pro 6 or MPW-GM (August 2001) can be used to build Emacs on the Mac OS Classic. On Mac OS X, Emacs can be built using the Developer Tools. See the INSTALL file in this directory for instructions on building Emacs. Read the Mac OS section of the on-line help to find out about how to use Emacs on the Mac. A number of things do not work yet: + Support for PostScript image type is not available. + Incorporate Apple's wrappers to be able to create a universal binary that unexecs on first run for the given architecture. If your Mac is connected to the Internet, report bugs by typing `M-x report-emacs-bug' or by choosing the entry `Send Bug Report...' in the `Help' menu. This will send the bug report to the address emacs-pretest-bug@gnu.org. Steven <steven.tamm@mac.com>