It can be set to any value at all, unfortunately.

The problem now is that non-cons/non-nil values are ignored.
The loop to repeatedly thinks there's input so it consumes 100% cpu, each
iteration seeing that it isn't a cons cell, so there's "nothing to do".

On Thu, Mar 10, 2016 at 12:25 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Andreas Schwab <schwab@suse.de>
> > Date: Thu, 10 Mar 2016 10:42:53 +0100
> > Cc: 22976@debbugs.gnu.org
> >
> > Eyal Lotem <eyal.lotem@gmail.com> writes:
> >
> > > As can be reproduced easily:
> > >
> > > (setq unread-command-events 1) -- emacs now at 100% CPU
> > > (setq unread-command-events nil) -- emacs OK again
> >
> > Don't do that then.
>
> Can unread-command-events be anything but nil or a cons cell?  If not,
> we could change the few tests of the value to explicitly ignore
> non-nil, non-cons values.  Do you see any immediate problems with such
> a change?
>
> Thanks.
>



-- 
Eyal