From: Anders Lindgren <andlind@gmail.com>
To: "James P. Ascher" <jpa4q@virginia.edu>
Cc: 22426@debbugs.gnu.org
Subject: bug#22426: 24.5; Crash from full-screen in OS X for emacs 24.5
Date: Mon, 25 Jan 2016 09:41:28 +0100 [thread overview]
Message-ID: <CABr8eba7P26TTsfmAPQkOvmaZfcERTCcRTSHCB6ePiep_4EsUg@mail.gmail.com> (raw)
In-Reply-To: <m17fiylfx6.fsf@virginia.edu>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
Hi!
> It seems that 25 fixes the problem. The bug does NOT occur with
>
> Emacs-2016-01-24_01-41-01-8cdb9ac0fb060366bc823de84ecdba258716addb-universal.dmg
> from that address. I also checked the build of 24 up there (
> Emacs-24.5-1-universal.dmg ) and it still has the same bug, but I can
> confirm that the bug is gone in that nightly build of 25.
>
This is great news! I will close the bug, but I will investigate the cause
of the regression I noticed.
I'm totally happy to help debug the problem in 24, as it would be an
> excuse to understand the development process better, but I'm also happy
> to wait for 25.1 to become stable, which seems imminent.
>
> Say the word and I'll figure out how to compile a debugging version of
> 24 (I just managed to codesign gdb), but I suspect that energy may be
> better spent on 25.
>
No need, as it is fixed in Emacs 25.
Of course, if you feel like contributing to NS interface in Emacs 25,
you're more than welcome, as the long time maintainer retired last year.
-- Anders
[-- Attachment #2: Type: text/html, Size: 1673 bytes --]
next prev parent reply other threads:[~2016-01-25 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 17:23 bug#22426: 24.5; Crash from full-screen in OS X for emacs 24.5 James P. Ascher
2016-01-24 21:46 ` Anders Lindgren
2016-01-24 23:24 ` James P. Ascher
2016-01-25 8:41 ` Anders Lindgren [this message]
2016-01-25 8:43 ` Anders Lindgren
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=CABr8eba7P26TTsfmAPQkOvmaZfcERTCcRTSHCB6ePiep_4EsUg@mail.gmail.com \
--to=andlind@gmail.com \
--cc=22426@debbugs.gnu.org \
--cc=jpa4q@virginia.edu \
/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.