[Top][All Lists]

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

Re: auctex on MacOSX

From: Juergen Fenn
Subject: Re: auctex on MacOSX
Date: Sun, 11 Apr 2021 14:47:17 +0200

Am 11.04.21 um 10:28 Uhr schrieb Uwe Brauer:
> Thanks but this based on a rather old Emacs version (24 or 25 if I am
> not mistaken).

I'm sorry to hear this. I was not aware that this is one of your
priorities. I recommended to use Aquamacs because it ususally works out
of the box wich MacTeX.

In case you or someone else is interested in Aquamacs development, I
would like to hand on two mails Win Treese has sent to the
Aquamacs-devel list recently. Pls see below.


-------- Weitergeleitete Nachricht --------
Betreff: [aquamacs-devel] Thinking about Aquamacs 4.0
Datum: Tue, 2 Feb 2021 22:14:33 -0500
Von: Win Treese <>
Antwort an:

Hi, all. The following is also posted on the Aquamacs GitHub issue
trackers at

This note is the beginning of a discussion about how to get Aquamacs
updated to a current version of the main Emacs distribution.

The next planned release of Aquamacs is 3.6, which should be in beta
soon. It has many bug fixes to the current codebase, which is based on
Emacs 25.3. Right now, there is no plan for a 3.7 release, but it could
happen if needed.

The next major release, tentatively called 4.0, will be Aquamacs based
on Emacs 28. It's a big jump, and there will probably be some messy parts.

There are a couple of ways to approach this, and I'd appreciate any
thoughts about what might work best. Whichever way we approach it, I
want to try to maintain the git history as best we can.

The core Emacs code for the Mac has changed a lot since Aquamacs was
first created, and diverged because there were different ideas at
different times. I'd like to end up bringing them closer together,
without sacrificing places where Aquamacs has improvements. Ultimately,
it would be nice if Aquamacs was a fairly clean add-on to the base
Emacs, but there's a lot of work to get there.

If I were undertaking the update entirely on my own, I would be tempted
to run a giant merge with the current Emacs code, hack through the merge
conflicts, and the debug the result.

If some of you are interested in helping out, we can approach it a
different way.

In rough terms, we have the following big areas of Aquamacs code:
1. Aquamacs-specific addons and configuration in Lisp code
2. Bundled packages from elsewhere (e.g, AUCTeX, ESS)
3. Aquamacs changes to base Emacs Lisp code
4. Aquamacs changes to base Emacs C/Objective C code
5. Other changes around the edges (documentation, auxiliary files, etc.)I

With a group working on it, we could break it out by focusing small
pieces of work on the Aquamacs features and Lisp files, stubbing out
anything that needs a new or changed interface in the C/Obj-C code.
Similarly, we could work on more isolated pieces of the merging the
C/Obj-C code, although some of it will of course be a bit tangled.

Or you might have some other ideas about how to approach this. I haven't
mapped out any of this in detail yet, but I'm interested in any thoughts
about how to go about it, and in finding out if anyone is interested in
working on it.




Win Treese
Aquamacs maintainer

-------- Weitergeleitete Nachricht --------
Betreff: [aquamacs-devel] Getting to Aquamacs on M1/Apple Silicon
Datum: Sat, 30 Jan 2021 13:44:27 -0500
Von: Win Treese <>
Antwort an:

I don’t have an M1 system myself yet, but I know some people are running
Aquamacs under Rosetta on M1 systems. If anyone is interested in getting
Aquamacs running natively on M1, we have an open issue about it on
Github at

I just posted an outline of the most obvious things that need to be done
there, and we can use that issue for any discussion about it.

For quick reference without having to look there, here’s what I wrote:

Here's an outline of the things I know need to be done for having
Aquamacs native on M1/Apple Silicon. I don't have an M1 system to work
with yet. I'm happy to work with anyone who wants to tackle any of it.

For Aquamacs on M1 as a separate distribution:

        • Look into what's been done for other Emacs distributions on M1.
        • See if Aquamacs will build and run for individual use on an M1
system, without including gnutls. (This is somewhat limited, because you
can't install packages this way, although you might be able to copy over
the files from an x86 setup).
        • See if gnutls and its package dependencies now works on M1. Better
yet, have it building via Homebrew. There may be some other dependencies
we end up needing, but that's the big one.
For Aquamacs on M1 as a universal binary (which would be nice, but not
essential to start):

        • Figure out how to tweak the Aquamacs build for this
        • Figure out how to build gnutls, etc., as libraries in universal form
(which I assume is theoretically possible, but I haven't looked into that)

There are probably some things I haven't though of yet.

I may eventually get to this, but I’m currently occupied with the rest
of the issue backlog and other work that needs to be done. In the
meantime, any help is appreciated!



reply via email to

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