unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: [PATCH] ; Do not overwrite prexisting contents of unread-command-events
Date: Sat, 25 Jul 2015 19:07:42 +0200	[thread overview]
Message-ID: <878ua4kvxd.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <1437843433-4931-1-git-send-email-dak@gnu.org> (David Kastrup's message of "Sat, 25 Jul 2015 18:57:13 +0200")


Unfortunately, recording macros with C-x ( ... C-x ) and replaying with
C-x e is still bleeding probably something like 15% of my events
synthesized from Midi when pressing chord buttons on an accordion
(3 immediately adjacent Midi events taking something like 2 bytes each
at 31250 bits/s, read in via an Emacs process filter function).

So the output of C-x e is somewhat shorter than the equivalent when
recording.

I suspect that code of the form

(let (unread-command-events)
   ...
 )

in the macro recording is at fault by letting material arrive in a
let-bound unread-command-events and not taking all of it out before
unbinding.

But at least most of the other opportunities for dropping
events/characters are addressed by this patch.

-- 
David Kastrup



  reply	other threads:[~2015-07-25 17:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-25 16:57 [PATCH] ; Do not overwrite prexisting contents of unread-command-events David Kastrup
2015-07-25 17:07 ` David Kastrup [this message]
2015-08-03 14:58   ` David Kastrup
2015-08-03 15:15     ` Artur Malabarba
2015-08-03 16:36       ` 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

  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=878ua4kvxd.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 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).