From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Questions about throw-on-input Date: Thu, 07 May 2020 21:58:58 -0400 Message-ID: References: <87r1vwxktw.fsf@gmail.com> <831rnvly58.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="103876"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Eli Zaretskii , emacs-devel To: yyoncho Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 08 03:59:39 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jWsId-000Quh-CG for ged-emacs-devel@m.gmane-mx.org; Fri, 08 May 2020 03:59:39 +0200 Original-Received: from localhost ([::1]:54414 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jWsIc-000248-DO for ged-emacs-devel@m.gmane-mx.org; Thu, 07 May 2020 21:59:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35938) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jWsI9-0001fF-QN for emacs-devel@gnu.org; Thu, 07 May 2020 21:59:09 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:28967) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jWsI8-0008UZ-9r; Thu, 07 May 2020 21:59:09 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 17FA3813D9; Thu, 7 May 2020 21:59:06 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id C5BA481479; Thu, 7 May 2020 21:58:59 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1588903139; bh=q9VFssqFjQuGzPGTeHB34wKDYEPY3XLToFHSmUY52TA=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=grixhCjozRGQCTvxe2Je8CUnO99d0j7rI8s7Wav93Sgy6wtU1v8jqMjSwgy4/Sm5T 137OG9ao5pthrNXA67aw12bb213fIUeAldYQbD7dTDnFtfq0YA7nKidtknLHnn07HM jm1pZbkfV1brAX8epnYbeau1Lnr1XTKnpQEvjy9x7XPVZMwdcC5kifikUXsU3yMh40 m2q573HYxJYUQfL3xL95V9J5vccc3bw8rKcgM/NgEn1gXnvXKn5mqwwEwanIrWiwD9 v+F/4f8KrbYiMJ0yCJz6t9Rd7Vcav2e8oZOx4FLtgolBeSNe2LgT1ACUffTC5fL1NO is0AprG8FwuqA== Original-Received: from alfajor (unknown [216.154.3.202]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 7C194120B37; Thu, 7 May 2020 21:58:59 -0400 (EDT) In-Reply-To: (yyoncho@gmail.com's message of "Fri, 8 May 2020 00:11:26 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/07 21:59:06 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:249232 Archived-At: > Out of curiosity, do you think that having a function > (process-events) which will process all keyboard(?) events > and resume the current invocation can be implemented easily? It can be implemented, but it won't have the desired semantics. If you want something robust you have 2 options: - write in an event-driven style (or CPS style) so that you can easily stop at various points in the program and stash the rest of the computation for later. - use a thread (which will basically do the same, but transparently, i.e. without the awkward programming style.) Stefan > AFAIK a lot of gui toolkits have that kind of function, e. g. > https://docs.microsoft.com/en-us/dotnet/api/system.windows.forms.application.doevents?view=netcore-3.1 > > IMO it will be very useful for certain cases. > > Thanks, > Ivan > > On Thu, May 7, 2020 at 3:37 PM Eli Zaretskii wrote: > >> > From: Ivan Yonchovski >> > Date: Thu, 07 May 2020 10:31:23 +0300 >> > >> > >> > 1. In the following example: >> > >> > (dotimes (_ 10) >> > (message "Length %s" >> > (length >> > (let (result) >> > (catch t >> > (let ((throw-on-input t)) >> > (dotimes (counter 10000000) >> > (push (number-to-string counter) result)))) >> > result)))) >> > >> > .. after I execute the following block each of the 10 computations will >> be >> > canceled after pressing C-n for example, how do I force the handling of >> > the command to be processed? I tried redisplay but it does not help. >> >> Invoking redisplay won't help because the commands which interrupted >> the inner loop (C-n) were not yet executed. Emacs will process them >> only after the outer loop ends, because that outer loop is the last >> command, and it is still being executed. Emacs doesn't perform >> commands in the middle of another command. >> >> > (message "Length %s" >> > (length >> > (let (result) >> > (catch t >> > (let ((throw-on-input t)) >> > (dotimes (counter 10000000) >> > (push (number-to-string counter) result)))) >> > result))) >> > >> > >> > (run-with-idle-timer >> > 0.0 >> > nil >> > (lambda () >> > (message "Length %s" >> > (length >> > (let (result) >> > (catch t >> > (let ((throw-on-input t)) >> > (dotimes (counter 10000000) >> > (push (number-to-string counter) result)))) >> > result))))) >> > >> > The issue is with the second block, it seems like throw-on-input is >> > disregarded when used in run-with-idle-timer. Can anyone confirm if this >> > is a bug/desired behavior or I should use something else if I want to >> > run cancelable tasks in on-idle? >> >> When the time function is run, Emacs binds inhibit-quit to t (so that >> the user's C-g would not interrupt the timer function, for example). >> And throw-on-input uses quitting to do its job. >> >> Why do you need to interrupt an idle timer like that? The usual way >> of doing this is not to call expensive functions in an idle timer, and >> if you have a lot of processing, divide them into small enough chunks >> and do it piecemeal. That's what jit-stealth font-lock does, for >> example. >>