From: Lars Ingebrigtsen <larsi@gnus.org>
To: Logan Perkins <logan@lp-programming.com>
Cc: 39687@debbugs.gnu.org
Subject: bug#39687: 26.3; Add customize-variable option for not locking keyboards
Date: Thu, 01 Oct 2020 20:44:30 +0200 [thread overview]
Message-ID: <877ds93hwx.fsf@gnus.org> (raw)
In-Reply-To: <6a23af03-d597-6e3e-ceb4-5fb1305a496a@lp-programming.com> (Logan Perkins's message of "Mon, 18 May 2020 18:15:15 -0700")
Logan Perkins <logan@lp-programming.com> writes:
> I *think* I have a patch that still fixes the current behavior, and
> does not reintroduce those two bugs, I've included it below.
> Basically, the fix for Bug#5095 should only be applied if we are in
> the right context. If we're not, the if block above puts a
> Qswitch_frame at the head of the side queue and triggers
> replay_entire_sequence, so we just skip the second check. It'll get
> run again and catch the interruption on the next pass, but in the
> right context.
Eli, did you have a chance to take a look at the proposed patch here?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-01 18:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 5:01 bug#39687: 26.3; Add customize-variable option for not locking keyboards Logan Perkins
2020-02-21 8:23 ` Eli Zaretskii
[not found] ` <32ea14fb-1ab8-186e-2534-4d3d2a56d6d8@lp-programming.com>
2020-02-22 9:27 ` Eli Zaretskii
2020-02-22 18:00 ` Logan Perkins
2020-05-19 1:15 ` Logan Perkins
2020-10-01 18:44 ` Lars Ingebrigtsen [this message]
2020-10-01 19:23 ` Eli Zaretskii
2021-07-21 15:57 ` Lars Ingebrigtsen
2021-07-21 17:52 ` Logan Perkins
2021-07-21 19:52 ` Eli Zaretskii
2021-07-21 22:08 ` Lars Ingebrigtsen
2021-07-21 22:44 ` Logan Perkins
2021-07-22 12:05 ` Lars Ingebrigtsen
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=877ds93hwx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=39687@debbugs.gnu.org \
--cc=logan@lp-programming.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.