[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Severe lossage from unread-command-events

From: David Kastrup
Subject: Severe lossage from unread-command-events
Date: Wed, 05 Aug 2015 17:46:50 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)


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


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: timer-test.el
Description: application/emacs-lisp

David Kastrup

reply via email to

[Prev in Thread] Current Thread [Next in Thread]