From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eyal Lotem Newsgroups: gmane.emacs.bugs Subject: bug#22976: 24.5; setting unread-command-events to non cons puts emacs in 100% CPU use Date: Thu, 10 Mar 2016 09:47:46 +0000 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11468f188a9e8c052daeb535 X-Trace: ger.gmane.org 1457603373 8630 80.91.229.3 (10 Mar 2016 09:49:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 10 Mar 2016 09:49:33 +0000 (UTC) Cc: 22976@debbugs.gnu.org To: Andreas Schwab Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Mar 10 10:49:15 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1adxDW-0004xY-Rk for geb-bug-gnu-emacs@m.gmane.org; Thu, 10 Mar 2016 10:49:15 +0100 Original-Received: from localhost ([::1]:47262 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adxDT-0002wR-4x for geb-bug-gnu-emacs@m.gmane.org; Thu, 10 Mar 2016 04:49:11 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58113) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adxDP-0002tz-5h for bug-gnu-emacs@gnu.org; Thu, 10 Mar 2016 04:49:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1adxDK-0005fN-FH for bug-gnu-emacs@gnu.org; Thu, 10 Mar 2016 04:49:07 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:45141) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adxDK-0005fH-80 for bug-gnu-emacs@gnu.org; Thu, 10 Mar 2016 04:49:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1adxDK-0007xQ-2n for bug-gnu-emacs@gnu.org; Thu, 10 Mar 2016 04:49:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eyal Lotem Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 10 Mar 2016 09:49:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22976 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 22976-submit@debbugs.gnu.org id=B22976.145760328430501 (code B ref 22976); Thu, 10 Mar 2016 09:49:02 +0000 Original-Received: (at 22976) by debbugs.gnu.org; 10 Mar 2016 09:48:04 +0000 Original-Received: from localhost ([127.0.0.1]:42264 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1adxCO-0007vt-1j for submit@debbugs.gnu.org; Thu, 10 Mar 2016 04:48:04 -0500 Original-Received: from mail-wm0-f54.google.com ([74.125.82.54]:33408) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1adxCM-0007vO-G8 for 22976@debbugs.gnu.org; Thu, 10 Mar 2016 04:48:02 -0500 Original-Received: by mail-wm0-f54.google.com with SMTP id l68so20870798wml.0 for <22976@debbugs.gnu.org>; Thu, 10 Mar 2016 01:48:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=z4YLy5EdQh46stPxQM6pOCFdqpWm2l9JVt+sPuJmBzA=; b=0l0Nkp8sY9EdJqzyQaPx6EQrk7mjNEQ5lqtkjm5Xvs0QRWvE+YSw5icaOTT7WG4v1U 4wXjbVEchYCPNnbKL2kI569wy6zi6g0+QwFmfsknBPtkn+XFVrUr9I4nIzJRce17akQP bLqOb4bZQkSjsDLUDQ3GDKLbGsVXWVf2L0ZwvHmCvwKmYipP+osYcpXLXo2HDN36olHQ Ss6gQVJLGtDJT3ZNDrCqagJ/GLYF2Blv6RyHR/rFjvuRMPU8qHrTGgwU8olu1s9HbhuA NHhmVlYpYerbql7pin7o024woqqMlKiNObhLZJr0FcE+L27tV8umEa4MO0FurYYq4bla p5Pg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=z4YLy5EdQh46stPxQM6pOCFdqpWm2l9JVt+sPuJmBzA=; b=OFmJ/hjTx+K3vQI/YzyRKsuvNFKLQ1vR6PSGasEpEuaIJ84h8Rd3b23s+cTSaZR4/3 PsOretw4OEoJdTnKr8Rsa6F9mH/MoVNa3IqfyxKivVb0qolQ+cGiBL3t5J4xQjpD1fAd VTpWDyRzg+Gf/YYcmFc9hhDqUASxGig9HOWpS1IC4Fp18/atJemsZoQrdJo9D02H7XAF SM/GzjdT3jF00tvyBpOHWVZGATq2uI+3Ro6C5Q39yg0hQhdcDYSpPYZhPvjeAJk1obFb YNSr6j4B+CFLBZ3+C2h5juBAnqLrQgG/IHugY9VJ4+L+P8Tz6tBpWTJThkiB+8wAtcXx mOdQ== X-Gm-Message-State: AD7BkJI1sKoPakEgnYl/MQ9rfHazvbbkQBWJZC+xpPsRjY2VWjJwUwnqcFfBWKKm2ChP6RZW2bPpsqjQ9X9OTg== X-Received: by 10.28.217.146 with SMTP id q140mr2593329wmg.85.1457603276871; Thu, 10 Mar 2016 01:47:56 -0800 (PST) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:114696 Archived-At: --001a11468f188a9e8c052daeb535 Content-Type: text/plain; charset=UTF-8 I don't, but some buggy packages I use do! Instead of wasting me hours chasing these bugs, why not output an explicit error and set the var to nil? This behavior caused the bug in the first place (subtle enough wrong behavior instead of explicit error made it go unnoticed). I'm not the first one to waste hours on this... On Thu, Mar 10, 2016, 11:42 Andreas Schwab wrote: > Eyal Lotem 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. > > Andreas. > > -- > Andreas Schwab, SUSE Labs, schwab@suse.de > GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 > "And now for something completely different." > --001a11468f188a9e8c052daeb535 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I don't, but some buggy packages I use do!

Instead of wasting me hours chasing these bugs, why not outp= ut an explicit error and set the var to nil?

This behavior caused the bug in the first place (subtle enou= gh wrong behavior instead of explicit error made it go unnoticed).

I'm not the first one to waste hours on this...


On Thu, Mar 10, 2016, 11:42= Andreas Schwab <schwab@suse.de>= ; wrote:
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.

Andreas.

--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint =3D 0196 BAD8 1CE9 1970 F4BE=C2=A0 1748 E4D4 88E3 0EEA = B9D7
"And now for something completely different."
--001a11468f188a9e8c052daeb535--