emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: can't compile master on MacOS 10.15 with fink


From: Uwe Brauer
Subject: Re: can't compile master on MacOS 10.15 with fink
Date: Tue, 23 Feb 2021 15:47:54 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

> On Mon, Feb 22, 2021 at 3:04 AM Uwe Brauer <oub@mat.ucm.es> wrote:

> Note: I lost regular access to macOS about a year and a half ago.


> 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.

I think I will stick to my Linux machine for the forseeable future, but
also want a stable and modern enough emacs to run the packages I use
most, namely auctex, gnus and org mode.
I would need, to get the hyper-super modifier business resolved. The
emacsformacox seems to take care of that, the fink compiled one on the
other hand does not (without digging into Xmodmap).




> 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.

Ok, I will give this a try, I don't think I will need the remote X
display stuff for the moment, but thanks for pointing that out to me.

Regards

Uwe 

Attachment: smime.p7s
Description: S/MIME cryptographic signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]