From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Severe lossage from unread-command-events
Date: Wed, 05 Aug 2015 17:46:50 +0200 [thread overview]
Message-ID: <87egjh4u1h.fsf@fencepost.gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
Hi,
run the included test file using
emacs -Q -l timer-test.el
and then open the generated dribble file /tmp/mydrib. On my computer,
it looks something like
0000000000000000001111111111111111111222222222222222222223333333333333333444444444444444444555555555555555556666666666666666667777777777777777778888888888888888899999999999999999
which means that of 4000 events having an effect in the scratch buffer,
about 5% (a non-deterministic amount) are actually recorded in the
dribble file. In particular, it looks like only the first of several
events placed into unread-command-events at one point of time will ever
see the dribble file. While I am only moderately interested in actually
generating a useful dribble file, the same holds for macro recording.
And I have an actual application which is severely impacted here.
Note that _all_ of the events (usually) are actually processed as input
in the *scratch* buffer. It is only the recording of them which falls
really, really flat on its face.
[-- Attachment #2: timer-test.el --]
[-- Type: application/emacs-lisp, Size: 463 bytes --]
[-- Attachment #3: Type: text/plain, Size: 20 bytes --]
--
David Kastrup
next reply other threads:[~2015-08-05 15:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 15:46 David Kastrup [this message]
2015-08-06 14:29 ` Severe lossage from unread-command-events Eli Zaretskii
2015-08-06 15:01 ` David Kastrup
2015-08-06 15:25 ` Eli Zaretskii
2015-08-06 15:46 ` David Kastrup
2015-08-06 16:21 ` Eli Zaretskii
2015-08-07 16:08 ` Stefan Monnier
2015-08-07 16:41 ` David Kastrup
2015-08-08 15:14 ` raman
2015-08-07 18:13 ` Eli Zaretskii
2015-08-06 15:33 ` David Kastrup
2015-08-06 16:10 ` Eli Zaretskii
2015-08-06 16:16 ` David Kastrup
2015-08-06 18:47 ` David Kastrup
2015-08-06 20:00 ` David Kastrup
2015-08-10 16:56 ` David Kastrup
2015-08-10 17:35 ` Eli Zaretskii
2015-08-10 17:47 ` David Kastrup
2015-08-10 18:17 ` Eli Zaretskii
2015-08-10 18:34 ` David Kastrup
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=87egjh4u1h.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.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 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.