From: "João Távora" <joaotavora@gmail.com>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: Po Lu <luangruo@yahoo.com>, Yuuki Harano <masm+emacs@masm11.me>,
52941@debbugs.gnu.org
Subject: bug#52941: 29.0.50; pgtk: characters typed into minibuffers inserted multiple times
Date: Tue, 11 Jan 2022 09:44:18 +0000 [thread overview]
Message-ID: <CALDnm52gAiH2-S_6rxgTtHmOL=ZxWHJaiqaoqKw8Zq=Tyf1GhQ@mail.gmail.com> (raw)
In-Reply-To: <87ilurnnby.fsf@melete.silentflame.com>
[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]
Thanks, Sean, that's very good investigation and I'll admit induces
a "phew" on my part ;-)
And yes, I'm pretty sure this will happen with icomplete-mode as
well.
João
On Tue, Jan 11, 2022 at 12:11 AM Sean Whitton <spwhitton@spwhitton.name>
wrote:
> Hello,
>
> On Sat 01 Jan 2022 at 04:14PM -07, Sean Whitton wrote:
>
> > If the system is under heavy load, and/or Emacs is compiled with debug
> > options which substantially slow it down, and fido-mode is enabled, then
> > typing quickly into the minibuffer can result in typed characters
> > inserted more than once. Here is how I can reproduce it:
> >
> > emacs -Q
> > M-x fido-mode RET
> > C-h v
> >
> > and quickly try to type "font-weight-table". This is what I get in the
> > minibuffer:
> >
> > font-weweweweweweweight-tatabe
> >
> > Although I made at least one typo (I didn't type the 'l'), I definitely
> > did not type 'we' and 'ta' that many times.
> >
> > I haven't been able to reproduce with icomplete-mode, but as the problem
> > does not occur consistently, I am not confident it does not occur with
> > icomplete-mode.
>
> It occurred to me to try --with-x-toolkit=lucid instead of --with-pgtk.
> Sure enough, I cannot reproduce the bug. So I think the problem is
> something about how pgtk receives and processes keyboard input.
>
> In summary: I can reproduce with pgtk running as a native Wayland
> application, and I cannot reproduce with the Lucid build running under
> Xwayland. In both cases, swaywm. I have retitled the bug.
>
> Thanks.
>
> --
> Sean Whitton
>
--
João Távora
[-- Attachment #2: Type: text/html, Size: 2282 bytes --]
next prev parent reply other threads:[~2022-01-11 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 23:14 bug#52941: 29.0.50; fido-mode: characters typed into minibuffers inserted multiple times Sean Whitton
2022-01-11 0:11 ` bug#52941: 29.0.50; pgtk: " Sean Whitton
2022-01-11 9:44 ` João Távora [this message]
2022-01-11 10:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-13 16:58 ` Sean Whitton
2022-01-14 0:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 21:30 ` Sean Whitton
2022-01-15 0:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-15 15:08 ` Yuuki Harano
2022-01-15 21:10 ` Sean Whitton
2022-01-16 8:45 ` Yuuki Harano
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='CALDnm52gAiH2-S_6rxgTtHmOL=ZxWHJaiqaoqKw8Zq=Tyf1GhQ@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=52941@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=masm+emacs@masm11.me \
--cc=spwhitton@spwhitton.name \
/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).