From: Ted Zlatanov <tzz@lifelogs.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs for Mac
Date: Fri, 04 Jan 2008 06:58:55 -0600 [thread overview]
Message-ID: <864pdtu4q8.fsf@lifelogs.com> (raw)
In-Reply-To: mailman.5671.1199393054.18990.help-gnu-emacs@gnu.org
On Thu, 03 Jan 2008 20:43:41 +0000 Alberto Simões <albie@alfarrabio.di.uminho.pt> wrote:
AS> For some time that the emacs I use on my Mac is a hand compiled
AS> one. CVS checkout, disable X11, enable Carbon.
AS> Now, I have a new mac, and thus, I need to recompile Emacs. CVS
AS> checked out, configure and... Carbon is deprecated.
AS> The question is: it is deprecated and no other solution is being developed?
The consensus (as I recall, this was a recent discussion with a LOT of
messages) was that after the next release of Emacs the Carbon/Cocoa
issue would be reconsidered, and probably the Cocoa port would be merged
in to replace the Carbon port. Meanwhile the CVS Carbon port is
deprecated and keyboard input there is broken AFAIK.
AS> And yes, there is aquamacs that sucks because tried to mimic mac-os
AS> specific key bindings, and there is emacs.app, that is the one I am
AS> using, but that is damn slow with flyspell (slower on my macbook pro
AS> than the hand built one on powerbook).
Emacs.App is the Cocoa port that's being considered. It has a mailing
list and lots of helpful users, so post about your flyspell problem
there and you should get a reply.
Ted
next parent reply other threads:[~2008-01-04 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5671.1199393054.18990.help-gnu-emacs@gnu.org>
2008-01-04 12:58 ` Ted Zlatanov [this message]
[not found] <1208022586.1678603.1612293425045.ref@mail.yahoo.com>
2021-02-02 19:17 ` Emacs for mac macandal--- via Users list for the GNU Emacs text editor
2021-02-02 22:49 ` Stefan Monnier
2021-02-03 3:23 ` Doug Davis
2008-01-03 20:43 Emacs for Mac Alberto Simões
2008-01-03 21:34 ` Peter Dyballa
2008-01-07 3:49 ` Mike Mattie
2008-01-07 9:43 ` Peter Dyballa
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=864pdtu4q8.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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.
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).