From: Eli Zaretskii <eliz@gnu.org>
To: sampo-emacs14@zxid.org
Cc: 18684@debbugs.gnu.org
Subject: bug#18684: 24.3; keystrokes come out of order
Date: Sat, 11 Oct 2014 09:54:49 +0300 [thread overview]
Message-ID: <8338av9juu.fsf@gnu.org> (raw)
In-Reply-To: <20141010224136.E120F6E688@mail.zxidp.org>
> From: sampo-emacs14@zxid.org
> Date: Fri, 10 Oct 2014 22:41:36 +0000 (GMT)
> Cc: sampo-emacs14@zxid.org
>
> When typing quickly, the charaters from keystrokes come out of order.
> For example typing 'f' 'o' 'r' 't' may come out as "ofrt" or sometimes
> fully inverse "trof" or some other combination.
>
> Typing faster makes the problem more likely to reproduce, but even
> quite normal typing speed has problems.
>
> Higher system load makes the problem more likely, but it manifests
> with load levels as low as 0.25.
>
> The problem is more prominent in buffers that have onerous font-lock
> configurations. E.g. the default syntax highlighting of c-mode
> makes the problem 4 times as likely as fundamental-mode.
>
> It seems to me that somehow the input queue processing is not
> strictly FIFO. Instead, the characters that pile up while other
> process is running, are all rendered in inverse order at some
> later time after some newer characters have already been rendered.
When this happens, does "C-h l" (that's the letter ell, not the digit
one) show the keys in the correct order or incorrect one?
Anyway, the Emacs input queue is a strict FIFO. I suspect some
optional package you use produces this strange effect, as I never saw
anything even close to what you describe.
Try analyzing your ~/.emacs and site-init files for possible culprits.
next prev parent reply other threads:[~2014-10-11 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 22:41 bug#18684: 24.3; keystrokes come out of order sampo-emacs14
2014-10-11 6:54 ` Eli Zaretskii [this message]
[not found] ` <mailman.10964.1413010577.1147.bug-gnu-emacs@gnu.org>
2014-10-31 14:36 ` Robert Marshall
2015-12-26 16:11 ` Lars Ingebrigtsen
2016-02-29 5:46 ` 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
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=8338av9juu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18684@debbugs.gnu.org \
--cc=sampo-emacs14@zxid.org \
/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).