From: Stefan Kangas <stefan@marxist.se>
To: Alan Third <alan@idiocy.org>
Cc: Robert Pluim <rpluim@gmail.com>, Nick <nick@tenpoint.co.nz>,
31371@debbugs.gnu.org
Subject: bug#31371: 26.1; Menu-bar stops working after search
Date: Tue, 05 Nov 2019 16:13:18 +0100 [thread overview]
Message-ID: <87y2wu5pbl.fsf@marxist.se> (raw)
In-Reply-To: <20191014131455.GB45622@breton.holly.idiocy.org> (Alan Third's message of "Mon, 14 Oct 2019 14:14:55 +0100")
Alan Third <alan@idiocy.org> writes:
> On Mon, Oct 14, 2019 at 02:44:21PM +0200, Stefan Kangas wrote:
>> > Thanks for testing. Updated patch attached.
>>
>> Thanks. Are there any objections to installing this fix?
>
> My only concern is that I believe the postponement stops lisp codie
> being run within the NS event loop, but if nobody’s seeing any crashes
> with the patch applied then I have no problem with it being applied.
>
> (caveat: I’ve not tried the patch myself)
Thanks. I haven't seen any crashes, but I haven't subjected it to any
heavy testing besides making sure that it solves the issue.
Perhaps we could apply it to give it some real world testing. We
could always revert the patch before Emacs 27.1 is released if it
turns out to cause any problems. Any objections to that plan?
Otherwise, I'll go ahead and do that in a couple of days.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2019-11-05 15:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 14:15 bug#31371: 26.1; Menu-bar stops working after search Nick Helm
2018-05-06 10:14 ` Alan Third
2018-05-07 2:48 ` Nick Helm
2018-05-08 5:24 ` Nick Helm
2018-05-08 21:40 ` Alan Third
2018-05-13 10:09 ` Nick Helm
2018-05-18 21:33 ` George Plymale II
2018-05-19 4:26 ` Nick Helm
2019-10-11 11:25 ` Stefan Kangas
2019-10-11 12:04 ` Robert Pluim
2019-10-14 1:50 ` Nick
2019-10-14 12:44 ` Stefan Kangas
2019-10-14 12:55 ` Robert Pluim
2019-10-14 13:14 ` Alan Third
2019-11-05 15:13 ` Stefan Kangas [this message]
2019-11-09 10:18 ` Stefan Kangas
2019-11-09 11:29 ` Alan Third
2019-12-31 10:29 ` Stefan Kangas
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=87y2wu5pbl.fsf@marxist.se \
--to=stefan@marxist.se \
--cc=31371@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=nick@tenpoint.co.nz \
--cc=rpluim@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).