[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Severe lossage from unread-command-events
From: |
Eli Zaretskii |
Subject: |
Re: Severe lossage from unread-command-events |
Date: |
Fri, 07 Aug 2015 21:13:56 +0300 |
> From: Stefan Monnier <address@hidden>
> Cc: David Kastrup <address@hidden>, address@hidden
> Date: Fri, 07 Aug 2015 12:08:44 -0400
>
> >> An element of the form (t . EVENT) forces EVENT to be added to that list.
> > This talks about a different kind of "recording", the one that stores
> > keyboard input in this-command-keys. My changes don't touch that (at
> > least I hope they don't ;-)
>
> I'm not sure it's really unrelated.
There are 2 separate calls to 2 different functions that do that, and
they are not called in the same places.
- Severe lossage from unread-command-events, David Kastrup, 2015/08/05
- Re: Severe lossage from unread-command-events, David Kastrup, 2015/08/06
- Re: Severe lossage from unread-command-events, Eli Zaretskii, 2015/08/06
- Re: Severe lossage from unread-command-events, David Kastrup, 2015/08/06
- Re: Severe lossage from unread-command-events, David Kastrup, 2015/08/06
- Re: Severe lossage from unread-command-events, David Kastrup, 2015/08/06
- Re: Severe lossage from unread-command-events, David Kastrup, 2015/08/10
- Re: Severe lossage from unread-command-events, Eli Zaretskii, 2015/08/10
- Re: Severe lossage from unread-command-events, David Kastrup, 2015/08/10
- Re: Severe lossage from unread-command-events, Eli Zaretskii, 2015/08/10
- Re: Severe lossage from unread-command-events, David Kastrup, 2015/08/10