From: Patrick Mahan <plmahan@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Using emacs on Macbook Pro M1 under Mac OS Monterey
Date: Tue, 8 Feb 2022 21:47:01 -0800 [thread overview]
Message-ID: <CAFDHx1JgY6UB=A-qy_1Nht-AbWkdwqNz-Uw5f6ybN5jYL-NLCg@mail.gmail.com> (raw)
In-Reply-To: <877da4516d.fsf@yahoo.com>
Thanks. I'm always nervous when I move up as I do not keep my emacs up to
date (I tend to just let the OS upgrades govern my upgrade path with
emacs). I usually break something with every major version jump, so this
is good to know that this is not the case here (so far :-)>)
Patrick
On Tue, Feb 8, 2022 at 4:33 PM Po Lu <luangruo@yahoo.com> wrote:
> Patrick Mahan <plmahan@gmail.com> writes:
>
> > Emacs version -
> >
> > GNU Emacs 27.2
> >
> > Copyright (C) 2021 Free Software Foundation, Inc.
> >
> > GNU Emacs comes with ABSOLUTELY NO WARRANTY.
> >
> > You may redistribute copies of GNU Emacs
> >
> > under the terms of the GNU General Public License.
> >
> > For more information about these matters, see the file named COPYING.
> >
> > I am seeing the following when launching emacs from the Terminal
> > application -
> >
> > mahan@MacBook-Pro-~ 345 > 2022-02-08 15:53:07.390
> > Emacs-arm64-12[8456:634837] It's not legal to call -layoutSubtreeIfNeeded
> > on a view which is already being laid out. If you are implementing the
> > view's -layout method, you can call -[super layout] instead. Break on
> void
> > _NSDetectedLayoutRecursion(void) to debug. This will be logged only
> > once. This
> > may break in the future.
> >
> > Is this something to do with my emacs configuration or emacs on the m1.
>
> AFAIK that was fixed in Emacs 28 and 29, so you might want to give the
> pretests a spin.
>
>
prev parent reply other threads:[~2022-02-09 5:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 23:59 Using emacs on Macbook Pro M1 under Mac OS Monterey Patrick Mahan
2022-02-09 0:33 ` Po Lu
2022-02-09 5:47 ` Patrick Mahan [this message]
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='CAFDHx1JgY6UB=A-qy_1Nht-AbWkdwqNz-Uw5f6ybN5jYL-NLCg@mail.gmail.com' \
--to=plmahan@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=luangruo@yahoo.com \
/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.
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).