From: David Kastrup <dak@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Severe lossage from unread-command-events
Date: Thu, 06 Aug 2015 18:16:13 +0200 [thread overview]
Message-ID: <877fp82y0i.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83h9ocs8hh.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 06 Aug 2015 19:10:50 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: David Kastrup <dak@gnu.org>
>> Cc: emacs-devel@gnu.org
>> Date: Thu, 06 Aug 2015 17:33:25 +0200
>>
>> Another data point would be Artur Malabarba's message about executing
>> keyboard macros which I answered in
>> <URL:http://lists.gnu.org/archive/html/emacs-devel/2015-08/msg00100.html>.
>
> Then perhaps Artur should try the patch I posted, and see if it helps.
>
>> >From glancing over your proposed fix, it's very much focused on dealing
>> with recording only.
>
> Not sure what exactly you mean by "recording" here. What I tried to
> do was not leave events that were not passed to record_char, except if
> those events are substituted by other events (e.g., when they are
> passed to an input method).
Well, Artur's problem was not concerned with recording but with replay.
So it would be sort of surprising if your patch made a difference for
it. At least sort of surprising to me. I think.
Anyway, got Emacs rebuilt and will now play with it.
--
David Kastrup
next prev parent reply other threads:[~2015-08-06 16:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 15:46 Severe lossage from unread-command-events David Kastrup
2015-08-06 14:29 ` 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 [this message]
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
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=877fp82y0i.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=eliz@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).