From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: can't compile master on MacOS 10.15 with fink
Date: Tue, 23 Feb 2021 15:47:54 +0100 [thread overview]
Message-ID: <87o8galu1x.fsf@mat.ucm.es> (raw)
In-Reply-To: CAO2hHWbveSyQcFWM7LZymJGrWajteyOVne32feoaipR3ea0dAA@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1817 bytes --]
> 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 #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2021-02-23 14:47 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
2021-02-23 14:47 ` Uwe Brauer [this message]
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
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=87o8galu1x.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).