From: Ian Eure <ian@digg.com>
To: Marc Tfardy <bum@cyk.cyk>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs for Mac OS X - questions
Date: Fri, 26 Jun 2009 21:04:27 -0700 [thread overview]
Message-ID: <0BC48B67-8274-4554-B566-C25AEE7F2F9C@digg.com> (raw)
In-Reply-To: <h20fif$9mp$1@news.onet.pl>
On Jun 25, 2009, at 11:27 AM, Marc Tfardy wrote:
> I plan to switch from windows to intel mac and Aquamacs and I don't
> want
> use windows under mac - neither in virtual machine nor as dual boot.
> Emacs is one of my main application so it is very important for me
> that
> all things are working as usual. Here my questions:
>
As other people have mentioned, you probably shouldn't use Aquamacs,
as it's geared towards users who are comfortable with Mac apps, rather
than Emacs.
Your options for Emacs on OS X break down into the Emacs 22-based and
23-based. All GUI Emacs 22-based distributions use the Carbon port.
Carbon will continue to exist in Snow Leopard, but it won't be usable
by 64-bit apps. Carbon-based Emacsen should continue to work just fine
with 10.6.
The Carbon port was removed from Emacs for version 23, and it was
replaced with a Cocoa port. All 23-based GUI Emacsen use the Cocoa port.
22-based Emacsen:
- Stock Emacs. OS X ships with Emacs 22.1.1, text-only.
- Aquamacs, which most people have covered. http://aquamacs.org
- Carbon Emacs. This is a distribution of Emacs 22 compiled with the
Carbon window-system, and some added packages.
- Emacs 22 from MacPorts. Newer than the version which ships with OS
X, text-only.
23-based Emacsen:
- Emacs-app from MacPorts. The CVS snapshot is five months out of
date, and the non-CVS build is version "23.0.0_NS-9.0rc3." I have no
idea what that means, since it doesn't resemble any of the pretest
versions of Emacs 23 released so far.
- Compile your own from CVS. It's very straightforward.
- Run my nightly builds. Vanilla CVS, with minor patching as
necessary to get stuff to work. I run them, and they work fine for me. http://atomized.org/wp-content/cocoa-emacs-nightly/
> - what GNU Emacs features do not working in Aquamacs? In "Appendix
> F - Emacs and Mac OS" is written:
>
> "Emacs built on Mac OS X supports most of its major features except
> display support of PostScript images. The following features of
> Emacs are not supported on Mac OS Classic: unexec (`dump-emacs'),
> asynchronous subprocesses (`start-process'), and networking
> (`open-network-stream'). As a result, packages such as Gnus, GUD,
> and Comint do not work. Synchronous subprocesses (`call-process')
> are supported on non-Carbon build, but specially-crafted external
> programs are needed. Since external programs to handle commands
> such as `print-buffer' and `diff' are not available on Mac OS
> Classic, they are not supported. Non-Carbon build on Mac OS
> Classic
> does not support some features such as file dialogs, drag-and-
> drop,
> and Unicode menus."
>
> Is it still true for Aquamacs?
>
I believe this was only applicable for Emacs running on Mac OS 9 and
less. I've never had any problem with these features with any Emacs
running on Mac OS X.
- Ian
next prev parent reply other threads:[~2009-06-27 4:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 18:27 Emacs for Mac OS X - questions Marc Tfardy
2009-06-25 18:56 ` Andrea Crotti
2009-06-26 4:46 ` Kevin Rodgers
2009-06-26 16:34 ` Marc Tfardy
2009-06-26 18:57 ` Nurullah Akkaya
2009-06-25 19:22 ` Tim Visher
2009-06-25 19:23 ` queries0
2009-06-25 21:32 ` Nurullah Akkaya
2009-06-26 16:40 ` Marc Tfardy
2009-06-29 23:21 ` Xah Lee
2009-06-30 3:23 ` queries0
2009-06-30 8:49 ` Peter Dyballa
2009-06-25 22:43 ` Peter Dyballa
[not found] ` <mailman.1258.1245957740.2239.help-gnu-emacs@gnu.org>
2009-06-26 2:29 ` Barry Margolin
2009-06-26 16:55 ` Marc Tfardy
2009-06-27 2:26 ` Barry Margolin
2009-06-30 0:28 ` Xah Lee
2009-07-02 18:57 ` Marc Tfardy
2009-07-02 20:26 ` Xah Lee
2009-06-26 22:49 ` Xah Lee
2009-06-27 4:04 ` Ian Eure [this message]
2009-06-27 10:35 ` Peter Dyballa
2009-06-28 23:27 ` David Reitter
2009-06-29 20:49 ` Marc Tfardy
2009-06-30 0:58 ` David Reitter
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=0BC48B67-8274-4554-B566-C25AEE7F2F9C@digg.com \
--to=ian@digg.com \
--cc=bum@cyk.cyk \
--cc=help-gnu-emacs@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.