From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.bugs Subject: bug#12447: 24.1.50; Stuck in garbage collection on OS X Date: Fri, 21 Sep 2012 11:31:51 +0800 Message-ID: <87ipb8m4pk.fsf@gnu.org> References: <505598C8.8070904@yandex.ru> <834nmys1ht.fsf@gnu.org> <5055AD8E.5020309@yandex.ru> <83zk4qqj4d.fsf@gnu.org> <5055C0EB.3040908@yandex.ru> <83wqzuqgzr.fsf@gnu.org> <5055D34F.1040800@yandex.ru> <83txuyqdtv.fsf@gnu.org> <5055E16E.1070604@yandex.ru> <83sjaiqaqb.fsf@gnu.org> <5055F69B.4020004@yandex.ru> <837grr1idg.fsf@gnu.org> <5059115B.8010407@yandex.ru> <83txuuzpqo.fsf@gnu.org> <5059965F.5030708@yandex.ru> <83obl2yr19.fsf@gnu.org> <5059F10C.6070806@yandex.ru> <83ipbaynku.fsf@gnu.org> <87a9wlz6e4.fsf@gnu.org> <83ehlwznsf.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1348198354 26481 80.91.229.3 (21 Sep 2012 03:32:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 21 Sep 2012 03:32:34 +0000 (UTC) Cc: 12447@debbugs.gnu.org, hanche@math.ntnu.no, dgutov@yandex.ru To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Sep 21 05:32:36 2012 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 1TEtyl-0005nl-R9 for geb-bug-gnu-emacs@m.gmane.org; Fri, 21 Sep 2012 05:32:35 +0200 Original-Received: from localhost ([::1]:55682 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEtyh-0005aH-Aa for geb-bug-gnu-emacs@m.gmane.org; Thu, 20 Sep 2012 23:32:31 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:36598) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEtyf-0005Zm-Lr for bug-gnu-emacs@gnu.org; Thu, 20 Sep 2012 23:32:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TEtye-0003jw-Bz for bug-gnu-emacs@gnu.org; Thu, 20 Sep 2012 23:32:29 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:36381) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TEtye-0003js-8h for bug-gnu-emacs@gnu.org; Thu, 20 Sep 2012 23:32:28 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1TEu0A-00047x-GP for bug-gnu-emacs@gnu.org; Thu, 20 Sep 2012 23:34:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Chong Yidong Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 21 Sep 2012 03:34:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 12447 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 12447-submit@debbugs.gnu.org id=B12447.134819841815833 (code B ref 12447); Fri, 21 Sep 2012 03:34:02 +0000 Original-Received: (at 12447) by debbugs.gnu.org; 21 Sep 2012 03:33:38 +0000 Original-Received: from localhost ([127.0.0.1]:45927 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1TEtzl-00047K-UC for submit@debbugs.gnu.org; Thu, 20 Sep 2012 23:33:38 -0400 Original-Received: from mail-pb0-f44.google.com ([209.85.160.44]:37580) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1TEtzi-00047B-CH for 12447@debbugs.gnu.org; Thu, 20 Sep 2012 23:33:35 -0400 Original-Received: by pbbjt11 with SMTP id jt11so4271504pbb.3 for <12447@debbugs.gnu.org>; Thu, 20 Sep 2012 20:31:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=+i/HfFy50b8chu2wJY5fbDWsA4Bb5Yws+9nvdCNHd/g=; b=siemM81su7DPlsoqtogQRH0/ZEeQpALMet2riKkT7LBIf/hDRpWkbAkWzG/lD/hZ40 uPKj53a5/L9JF6PoBqRtU1Ke0vZ7Qj6+v714PrlW/OqMIPmajDoA5f3X3H78mpHySsQq pkFOJBn6Wp9bXb/r0ZeHjIp6qBXruJXxX26fasYJ99BNOtZDO7OHlHLoNx464TLJbPQp jqjI5pGtqzmMBNNldS2UiCqy13wTZyRYeC829htS4+PGPF8W0YD6dPqgq1FjNAqx5mtf Pc0m53zZJ03jyRbcKgp6Ew1GCYsGFnDou8Zp3kjj/wURRGNrLD99BU3pt0qCDl+I62s/ CCqA== Original-Received: by 10.66.85.8 with SMTP id d8mr10088780paz.30.1348198318598; Thu, 20 Sep 2012 20:31:58 -0700 (PDT) Original-Received: from ulysses ([155.69.19.149]) by mx.google.com with ESMTPS id kj10sm4427902pbc.72.2012.09.20.20.31.54 (version=SSLv3 cipher=OTHER); Thu, 20 Sep 2012 20:31:57 -0700 (PDT) In-Reply-To: <83ehlwznsf.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 20 Sep 2012 19:01:20 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 140.186.70.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:64671 Archived-At: Eli Zaretskii writes: >> When `run-with-idle-timer' is called from an idle timer, we could >> interpret it to mean "run the function the next time Emacs becomes idle >> for SECS seconds, not including the current period of idleness". > > I could think of some legitimate uses of the current behavior, though. > For example, imagine an idle timer that gets run after 1 sec of > idleness, does something quick and simple, and then calls itself or > another time with a larger timeout value, at which time it will do > something different, perhaps more complex. I see no reason to > forcibly prevent such use cases. It would still be possible to get the old behavior by calling lower-level timer functions used by `run-with-idle-timer'. > It is also in line with Emacs behavior since about forever. The > possibility of an infloop was a side effect of another bugfix. With > that possibility hopefully taken care of, we have no reason to change > old behavior, which evidently at least one external package relies > upon. What is the package that relies on the old behavior?