From: "John Wiegley" <johnw@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: Matthew Bauer <mjbauer95@gmail.com>, emacs-devel@gnu.org
Subject: Re: bug#26323: 25.1; Closing frames (in fullscreen) under Mac OS cause immediate crash
Date: Mon, 19 Mar 2018 18:05:30 -0700 [thread overview]
Message-ID: <m2fu4vpndx.fsf@newartisans.com> (raw)
In-Reply-To: <20180319122340.GA8353@breton.holly.idiocy.org> (Alan Third's message of "Mon, 19 Mar 2018 12:23:40 +0000")
>>>>> "AT" == Alan Third <alan@idiocy.org> writes:
AT> Yes, 10.10 doesn’t support the tabs command. emacsformacosx.com builds on
AT> 10.9 the last time I looked, so yes, that’s what’s going on there.
AT> Please try adding
AT> -DMAC_OS_X_VERSION_MAX_ALLOWED=101200
AT> to CFLAGS.
I can confirm that this resolves the issue for me. In fact, now each created
frame gets its own space, and I can even have a non-fullscreen frame in my
main space, with the other frames being their own spaces. And no more crashes
when closing a fullscreen frame. Thank you!
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2018-03-20 1:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 0:54 bug#26323: 25.1; Closing frames (in fullscreen) under Mac OS cause immediate crash Matthew Bauer
2018-03-16 10:47 ` Alan Third
2018-03-16 18:12 ` David Reitter
2018-03-18 11:15 ` Alan Third
2018-03-18 11:17 ` David Reitter
2018-03-18 11:30 ` Alan Third
2018-03-18 18:14 ` John Wiegley
2018-03-18 20:14 ` Alan Third
2018-03-19 0:37 ` Nick Helm
2018-03-19 12:29 ` Alan Third
2018-03-19 2:05 ` Matthew Bauer
2018-03-19 12:23 ` Alan Third
2018-03-20 1:05 ` John Wiegley [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-10 20:52 Noah Sussman
2018-07-12 20:51 ` Alan Third
2018-07-13 2:16 ` Radon Rosborough
2018-07-13 20:25 ` Noah Sussman
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=m2fu4vpndx.fsf@newartisans.com \
--to=johnw@gnu.org \
--cc=alan@idiocy.org \
--cc=emacs-devel@gnu.org \
--cc=mjbauer95@gmail.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.
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).