From: Jochem Huhmann <joh@gmx.net>
Subject: Re: emacs and osx
Date: Wed, 13 Apr 2005 17:18:11 +0200 [thread overview]
Message-ID: <m2k6n6n1sc.fsf@nova.revier.com> (raw)
In-Reply-To: _D97e.1227972$35.44954684@news4.tin.it
Bob Hunter <catdogbeloved@yahoo.com> writes:
> Hello,
>
> there are a few ports of emacs to osx, and it is unclear whether the
> efforts are merging into the main gnu source code.
These "ports" are AFAIK nothing else than compiled CVS-Emacsen, spiced
up with some additional keybindings and such.
OK, there is somewhere a Cocoa version of an ancient Emacs, based on
earlier work to port Emacs to NeXTStep. I don't know if it's that easy
to merge this into the main (current) code...
> In principle, one should be able to download the latest from gnu and
> compile autonomously under osx, with no need to download old
> out-of-sync binaries.
Exactly. Get the latest Emacs from the CVS, configure, make, install,
enjoy. It just works. This posting is written with a Emacs running on
Mac OS X, along with Carbon-GUI, anti-aliased fonts and everything,
compiled straight from the sources.
> I wonder what refrains the individual projects to work in a joint
> effort, to finally deliver this port, as osx is now in its fourth
> major release.
I guess as soon as there is a formal release of a new major Emacs
version, you will have a more or less "official" package. It's just that
there is (right now) nothing to "deliver", because there is not a
release yet.
BTW: All this chaos is not limited to Emacs. Look for almost any Open
Source app and you will find at least two or three different "ports" to
OS X floating around the net. There is Fink, darwinports and then
individual (binary) packages done by well-meaning people. Ever installed
a LaTeX system on OS X? I've been going through this just yesterday and
I can tell you, this is a hell of a mess. The average Linux- or
BSD-Distribution is lightyears ahead in terms of package management and
discipline among the porters. Apple made a terrible mistake by not
including a decent package management system along with a server
infrastructure right from the beginning, IMHO.
Jochem
--
"A designer knows he has arrived at perfection not when there is no
longer anything to add, but when there is no longer anything to take away."
- Antoine de Saint-Exupery
next prev parent reply other threads:[~2005-04-13 15:18 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 14:02 emacs and osx Bob Hunter
2005-04-13 13:30 ` Gian Uberto Lauri
2005-04-13 14:56 ` Peter Dyballa
2005-04-13 14:53 ` Sébastien Kirche
2005-04-13 15:18 ` Jochem Huhmann [this message]
2005-04-13 15:44 ` Bob Hunter
2005-04-13 16:04 ` Bob Hunter
2005-04-13 16:27 ` David Kastrup
2005-04-13 16:38 ` Bob Hunter
2005-04-13 17:01 ` David Kastrup
2005-04-13 17:10 ` Lute Kamstra
2005-04-13 17:13 ` David Kastrup
2005-04-14 1:48 ` Miles Bader
2005-04-14 1:57 ` Miles Bader
2005-04-13 17:05 ` Lute Kamstra
2005-04-13 17:27 ` Peter Dyballa
2005-04-13 16:57 ` Lute Kamstra
2005-04-13 17:19 ` Bob Hunter
2005-04-13 17:52 ` David Kastrup
2005-04-13 18:08 ` Bob Hunter
2005-04-13 18:11 ` Bob Hunter
2005-04-13 18:21 ` David Kastrup
2005-04-13 18:34 ` Bob Hunter
2005-04-13 19:02 ` Lute Kamstra
2005-04-13 21:01 ` Ismael Valladolid Torres
[not found] ` <mailman.1408.1113424532.2895.help-gnu-emacs@gnu.org>
2005-04-13 21:13 ` David Kastrup
2005-04-13 22:51 ` Joe Corneli
2005-04-13 19:19 ` Thien-Thi Nguyen
2005-04-13 19:57 ` David Kastrup
2005-04-13 23:46 ` Bob Hunter
2005-04-13 17:19 ` Chris F.A. Johnson
2005-04-13 17:43 ` Eli Zaretskii
2005-04-13 18:44 ` Ismael Valladolid Torres
2005-04-13 19:21 ` emacs and osx, Tetris Peter Dyballa
[not found] ` <mailman.1392.1113416407.2895.help-gnu-emacs@gnu.org>
2005-04-13 19:07 ` emacs and osx Lute Kamstra
2005-04-13 20:04 ` David Kastrup
2005-04-22 7:48 ` Rogério Brito
2005-04-22 14:50 ` Chris Menzel
2005-04-25 21:08 ` Jochem Huhmann
2005-05-02 0:29 ` Stefan Monnier
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=m2k6n6n1sc.fsf@nova.revier.com \
--to=joh@gmx.net \
/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).