From: Tim Cross <theophilusx@gmail.com>
To: Matt Armstrong <matt@rfc20.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: installing or compiling GNU emacs on Mac Catalina (fink for the moment)
Date: Wed, 24 Feb 2021 12:41:01 +1100 [thread overview]
Message-ID: <CAC=50j9kORLEFGCVyNNc3o-VizWL6PP3xs-3xd-n6f=Cu6UxqA@mail.gmail.com> (raw)
In-Reply-To: <m235xmxtvy.fsf@matts-mbp-2016.lan>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
I just checked and it still supports --HEAD as an option. The other options
do seem to be gone, but it looks like it builds with --with-cocoa
--with-modules --with-libsvg, though it would be necessary to look at the
details of the recipe to confirm. I would expect it is built with the same
options as the binary cask version.
On Wed, 24 Feb 2021 at 10:10, Matt Armstrong <matt@rfc20.org> wrote:
> Tim Cross <theophilusx@gmail.com> writes:
>
> > If you go with the vanilla emacs homebrew recipe, you can add a command
> > line option to have it build from the current repo HEAD. This is not a
> > bad option if you want to run latest bleeding edge. I don't tend to do
> > that because I prefer the stability of a released version when on the
> > mac.
>
> Just a FYI, as of two years ago it appears that Homebrew's vanilla emacs
> formula hard codes --without-ns and does not support --HEAD. See
> https://github.com/Homebrew/homebrew-core/pull/36070
>
--
regards,
Tim
--
Tim Cross
[-- Attachment #2: Type: text/html, Size: 1662 bytes --]
next prev parent reply other threads:[~2021-02-24 1:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 18:26 installing or compiling GNU emacs on Mac Catalina (fink for the moment) Uwe Brauer
2021-02-22 0:11 ` Doug Davis
2021-02-22 7:36 ` Uwe Brauer
2021-02-22 1:26 ` Tim Cross
2021-02-22 7:40 ` Uwe Brauer
2021-02-22 19:32 ` Tim Cross
2021-02-23 23:10 ` Matt Armstrong
2021-02-24 1:41 ` Tim Cross [this message]
2021-02-24 5:10 ` Matt Armstrong
2021-02-22 5:43 ` Pankaj Jangid
2021-02-22 7:41 ` Uwe Brauer
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='CAC=50j9kORLEFGCVyNNc3o-VizWL6PP3xs-3xd-n6f=Cu6UxqA@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=matt@rfc20.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).