From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Proposal for a new mechanism for delayed stuff Date: Fri, 04 Jan 2013 00:34:17 +0100 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 1357256074 11364 80.91.229.3 (3 Jan 2013 23:34:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 3 Jan 2013 23:34:34 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 04 00:34:50 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 1TquJF-00040R-AM for ged-emacs-devel@m.gmane.org; Fri, 04 Jan 2013 00:34:49 +0100 Original-Received: from localhost ([::1]:50244 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TquJ0-0004LT-3t for ged-emacs-devel@m.gmane.org; Thu, 03 Jan 2013 18:34:34 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:33841) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TquIu-0004J8-UO for emacs-devel@gnu.org; Thu, 03 Jan 2013 18:34:31 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TquIr-0003O9-Vr for emacs-devel@gnu.org; Thu, 03 Jan 2013 18:34:28 -0500 Original-Received: from hermes.netfonds.no ([80.91.224.195]:52457) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TquIr-0003Np-PE for emacs-devel@gnu.org; Thu, 03 Jan 2013 18:34:25 -0500 Original-Received: from cm-84.215.51.58.getinternet.no ([84.215.51.58] helo=stories.gnus.org) by hermes.netfonds.no with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1TquIj-0004cs-Gb; Fri, 04 Jan 2013 00:34:17 +0100 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAKlBMVEXq5uSajogHAQEsJCUH AADFvLdOREUMBQetoZv////+//79/f0ZEhN9cW7hirBVAAACU0lEQVQ4jXWUoY7bQBCGlxgdWlKZ LHGtBucs+Q4YWZZKj6xkUlJLRg7JSTVJgYFTg/YB7DxBUlJ6F1ZLCdmC6FSj23fpP+vNKVGT0Spy 9vPM7Mz8XrZuLxtrt8+b9Tnt2nbdsg7g56Y9RV232cLjed2RR7f9xZiUadNUB6HzJ7bSesjzPAuO lmVhGIQAUUR/7U8fRVG220UKQJ7ZAxutZStVntoi1FpX2oXH2f6kD/MZsg4GzD1rcRLbpwmAffS9 BBZj+VgEfNpOsPwRJB78jEdMb8cLpfYlcIxofmwAXBPfC/X+XjYiW/QByrU5Yj/2wsL7+Df98bLo w5l+PSb34fHZS+5TQSDXt0eAbOGtl3xwbaj523ERau4n7zmACvLM1kEFeAHO+5XrolRo8OhhSgOI /SkfihKxgt82FA7lBWjMQQCUqrcARQAs0KCDzu8AVF9Ozrr7iEneTUrTA4BgbyehTicDwByZVlyj D5Hd9OYG1FBGLZmDocqUv34ZOcCBc7epCWLi8tu0qaCaAIBzIjAIwZFNOswQlVTCMX1ecQ5CtpwN pDKApoGLADQmxCg+AxpK0VQIWGkhskj1ygguJURuHFB8ogEaJULJ9LoBXLtLKFWRRwuVQ+QUHgfX 03dZQC14Yt0NCI5poonhz5CrEayMkh1KhBwi63vTMwKOFTpQJYrs8QjqFM1A8pqI2L2MTabKTQGo 0EXpy7B4AweuD8g609yt0++6CI7A9EJQwxBSc/tBUh2b8dP+7wKQ8srNcLO9eGuw1pEPl0Hbbq+B Kzmu2D8T3fPC8aHMQAAAAABJRU5ErkJggg== X-Now-Playing: Cortex's =?iso-8859-1?Q?=5FG=F6teborg=5F=3A?= "Nicotine" In-Reply-To: (Stefan Monnier's message of "Thu, 03 Jan 2013 11:47:06 -0500") User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3.50 (gnu/linux) X-MailScanner-ID: 1TquIj-0004cs-Gb MailScanner-NULL-Check: 1357860857.71931@vt1Lo37zrKKZA34dbJ0HxQ X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.224.195 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:156066 Archived-At: Stefan Monnier writes: >> 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? Or is that too difficult? Anyway, if `current-state-message' is easy to implement, I'm all for getting that. :-) -- (domestic pets only, the antidote for overdose, milk.) bloggy blog http://lars.ingebrigtsen.no/