From: Eli Zaretskii <eliz@gnu.org>
To: Eyal Lotem <eyal.lotem@gmail.com>
Cc: schwab@suse.de, 22976@debbugs.gnu.org
Subject: bug#22976: 24.5; setting unread-command-events to non cons puts emacs in 100% CPU use
Date: Thu, 10 Mar 2016 12:39:00 +0200 [thread overview]
Message-ID: <834mcemxbv.fsf@gnu.org> (raw)
In-Reply-To: <CALA94fOzDcKqV7LU=ujV4495CpYzDr1G6jDgqO22qf61Ekm_4Q@mail.gmail.com> (message from Eyal Lotem on Thu, 10 Mar 2016 12:34:08 +0200)
> Date: Thu, 10 Mar 2016 12:34:08 +0200
> From: Eyal Lotem <eyal.lotem@gmail.com>
> Cc: Andreas Schwab <schwab@suse.de>, 22976@debbugs.gnu.org
>
> It can be set to any value at all, unfortunately.
That's not what I asked. I asked whether non-nil, non-cons values
have any meaning in unread-command-events.
> 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".
Exactly. So these values aren't ignored, they create an illusion that
some input is available. I was thinking about ignoring them entirely,
i.e. treating such values as nil (and maybe even silently replacing
them with nil).
The question is: would that kind of change break something?
next prev parent reply other threads:[~2016-03-10 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 8:37 bug#22976: 24.5; setting unread-command-events to non cons puts emacs in 100% CPU use Eyal Lotem
2016-03-10 9:42 ` Andreas Schwab
2016-03-10 9:47 ` Eyal Lotem
2016-03-10 10:25 ` Eli Zaretskii
2016-03-10 10:34 ` Eyal Lotem
2016-03-10 10:39 ` Eli Zaretskii [this message]
2016-03-10 12:40 ` Eyal Lotem
2016-03-26 8:54 ` Eli Zaretskii
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=834mcemxbv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22976@debbugs.gnu.org \
--cc=eyal.lotem@gmail.com \
--cc=schwab@suse.de \
/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).