all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Sat, 9 Nov 2019 11:18:36 +0100	[thread overview]
Message-ID: <CADwFkm=KFdsYvjQdCSHgT=V+URgKiZW9CiH1+Qey70JzjfZ4mg@mail.gmail.com> (raw)
In-Reply-To: <87y2wu5pbl.fsf@marxist.se>

Stefan Kangas <stefan@marxist.se> writes:

> 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.

No objections within 4 days, so I've now pushed the fix to master as
commit 6daa80d04e.  I'll leave the bug open for another couple of
weeks.  Please report here if you see any issues related to this
patch.

Best regards,
Stefan Kangas





  reply	other threads:[~2019-11-09 10:18 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
2019-11-09 10:18           ` Stefan Kangas [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkm=KFdsYvjQdCSHgT=V+URgKiZW9CiH1+Qey70JzjfZ4mg@mail.gmail.com' \
    --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 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.