From: Alan Third <alan@idiocy.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 55687@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#55687: 29.0.50; make-frame chid frame crash/regression from dfa3e6f424
Date: Sun, 29 May 2022 17:08:45 +0100 [thread overview]
Message-ID: <YpOajet3YscwbT8g@idiocy.org> (raw)
In-Reply-To: <CAHyO48wcXo_Q3Dwm+vs=6A40ht_YMSfifivtS9jbK91BOwuvtQ@mail.gmail.com>
On Sun, May 29, 2022 at 08:52:07AM -0400, Aaron Jensen wrote:
> Interesting. Luckily, I have never run across this other then while
> trying to repro the first bug I reported here. Alan, any ideas? Does
> this crash for you?
Works fine for me. You could maybe try something like this:
--- a/src/nsterm.m
+++ b/src/nsterm.m
@@ -7773,6 +7773,9 @@ - (instancetype) initFrameFromEmacs: (struct frame *)f
[self setLayerContentsPlacement:NSViewLayerContentsPlacementTopLeft];
#endif
+ /* toolbar support */
+ [(EmacsWindow*)[self window] createToolbar:f];
+
if (ns_drag_types)
[self registerForDraggedTypes: ns_drag_types];
@@ -8934,9 +8937,6 @@ - (instancetype) initWithEmacsFrame: (struct frame *) f
if ([col alphaComponent] != (EmacsCGFloat) 1.0)
[self setOpaque:NO];
- /* toolbar support */
- [self createToolbar:f];
-
/* macOS Sierra automatically enables tabbed windows. We can't
allow this to be enabled until it's available on a Free system.
Currently it only happens by accident and is buggy anyway. */
--
Alan Third
next prev parent reply other threads:[~2022-05-29 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 3:40 bug#55687: 29.0.50; make-frame chid frame crash/regression from dfa3e6f424 Aaron Jensen
2022-05-28 6:29 ` Eli Zaretskii
2022-05-28 20:11 ` Aaron Jensen
2022-05-29 5:36 ` Eli Zaretskii
2022-05-29 12:52 ` Aaron Jensen
2022-05-29 16:08 ` Alan Third [this message]
2022-05-29 17:46 ` Aaron Jensen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YpOajet3YscwbT8g@idiocy.org \
--to=alan@idiocy.org \
--cc=55687@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.