From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Proposal for a new mechanism for delayed stuff Date: Thu, 03 Jan 2013 20:56:31 -0500 Message-ID: References: <87pq1y46ao.fsf@gnus.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1357264596 12114 80.91.229.3 (4 Jan 2013 01:56:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 4 Jan 2013 01:56:36 +0000 (UTC) Cc: emacs-devel@gnu.org To: Lars Magne Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 04 02:56:52 2013 Return-path: Envelope-to: ged-emacs-devel@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 1TqwWg-0003xk-Vw for ged-emacs-devel@m.gmane.org; Fri, 04 Jan 2013 02:56:51 +0100 Original-Received: from localhost ([::1]:41003 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TqwWR-0001Du-Um for ged-emacs-devel@m.gmane.org; Thu, 03 Jan 2013 20:56:35 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:35534) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TqwWQ-0001Dp-1F for emacs-devel@gnu.org; Thu, 03 Jan 2013 20:56:34 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TqwWP-0000Wo-3n for emacs-devel@gnu.org; Thu, 03 Jan 2013 20:56:33 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:54987) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TqwWP-0000Wi-03 for emacs-devel@gnu.org; Thu, 03 Jan 2013 20:56:33 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtkGAG6Zu09FxK5W/2dsb2JhbABEgXuyFoEIghUBAQQBViMFCws0EhQYDSSIHAW6CZBEA4hCmnGBWIMH X-IronPort-AV: E=Sophos;i="4.75,637,1330923600"; d="scan'208";a="211318795" Original-Received: from 69-196-174-86.dsl.teksavvy.com (HELO fmsmemgm.homelinux.net) ([69.196.174.86]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 03 Jan 2013 20:56:32 -0500 Original-Received: by fmsmemgm.homelinux.net (Postfix, from userid 20848) id A029CAE3F0; Thu, 3 Jan 2013 20:56:31 -0500 (EST) In-Reply-To: (Lars Magne Ingebrigtsen's message of "Fri, 04 Jan 2013 00:34:17 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:156068 Archived-At: >>> Sure, that would also handle the "tell the user what's going on" use >>> case, and we could have a convenience macro `with-current-state-message' >>> that would simply be an `unwind-protect' to clear out the state message. >> Yes, the advantage is that the message can be displayed even if we're in >> the middle of uninterruptible Elisp code. > Well, presumably if we can display `current-state-message' in > uninterruptible Elisp code, we could also do the `with-timeout-forms' > things in the uninterruptible Elisp code? No, because that would mean running arbitrary code in the middle of "uninterruptible Elisp code", which is contrary to the idea of "uninterruptible". > Anyway, if `current-state-message' is easy to implement, I'm all for > getting that. :-) I don't know if it is. Stefan