Subject: bug#23980: 25.0.95; Events put in `unread-command-events' can be wrongly handled

From: Dmitry Gutov <[email-masked]>
Date: Tue, 20 Feb 2018 23:16:47 +0200

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).