From: chad <yandros@gmail.com>
To: EMACS development team <emacs-devel@gnu.org>
Subject: Re: can't compile master on MacOS 10.15 with fink
Date: Mon, 22 Feb 2021 14:49:48 -0800 [thread overview]
Message-ID: <CAO2hHWbveSyQcFWM7LZymJGrWajteyOVne32feoaipR3ea0dAA@mail.gmail.com> (raw)
In-Reply-To: <875z2k1i0k.fsf@mat.ucm.es>
[-- Attachment #1: Type: text/plain, Size: 1939 bytes --]
On Mon, Feb 22, 2021 at 3:04 AM Uwe Brauer <oub@mat.ucm.es> wrote:
> I seem to remember that you are a (long term) Mac user, what is your
> opinion about the one provided by emacsformacox?
>
Note: I lost regular access to macOS about a year and a half ago.
The emacsformacosx option is solid for end-users, but I think still less
good for developers (caveat: not so for developers interested in helping
make a stable "emacsformacosx" package for macos users, versus people
interested in latest-and-greatest emacs HEAD development). It replaces fat
binaries with a ruby-based launcher that figures out which binary to run.
This might bother or you not (it bothered me, once upon a time). Beyond
that it seemed to be a faithful version of GNU Emacs built for macos, and
offers nightly builds for closing some of the gap I mentioned above.
An alternative is the "mac port", which replaces the ns specific code in
the GNU Emacs mainline with code that uses a different mac-specific
toolkit. This has the advantage that the toolkit code it uses is more
current and better maintained (the toolkit code used by the ns port is
potentially at/beyond its theoretical end of support), and the downside
that it doesn't support the non-macOS nextstep codebase. In practice, the
mac port is pretty popular, because it removes some rough edges that the ns
port basically can't avoid. You can find more information about the mac
port at https://bitbucket.org/mituharu/emacs-mac/src/master/ and/or you can
use the popular homebrew packaging by user railwaycat.
Although my personal experience is a bit dated at this point, about a
decade of experience lead me to the conclusion that either the ns or mac
ports were better under macos UNLESS you also want to be able to open
frames on remote X displays. I mostly used the ns port built directly from
the GNU Emacs HEAD. I would be surprised if that had changed in the
meantime.
Hope that helps!
~Chad
[-- Attachment #2: Type: text/html, Size: 2499 bytes --]
next prev parent reply other threads:[~2021-02-22 22:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 7:38 can't compile master on MacOS 10.15 with fink Uwe Brauer
2021-02-22 9:07 ` Robert Pluim
2021-02-22 11:03 ` Uwe Brauer
2021-02-22 11:23 ` Alan Third
2021-02-23 20:50 ` Uwe Brauer
2021-02-23 22:51 ` Alan Third
2021-02-22 14:58 ` Robert Pluim
2021-02-22 22:49 ` chad [this message]
2021-02-23 14:47 ` Uwe Brauer
2021-02-23 19:00 ` Alan Third
2021-02-23 20:03 ` chad
2021-02-24 6:47 ` Richard Stallman
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=CAO2hHWbveSyQcFWM7LZymJGrWajteyOVne32feoaipR3ea0dAA@mail.gmail.com \
--to=yandros@gmail.com \
--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.