|
| From: | Dmitry Gutov |
| Subject: | bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled |
| Date: | Tue, 20 Feb 2018 23:16:47 +0200 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Thunderbird/59.0 |
On 2/20/18 8:37 PM, Eli Zaretskii wrote:
I'd need someone (Chris?) to tell which situations cause (t SOMETHING) be put into unread-command-events. If these situations are rare enough, maybe we can risk it.
At least one of the places that do that is sit-for. See the long comment at the end of its definition (I don't really understand its last sentence, FWIW).
| [Prev in Thread] | Current Thread | [Next in Thread] |