From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: System calls without error checks in w32 Date: Tue, 8 Jun 2010 01:35:58 +0200 Message-ID: References: <4C037EFE.4040304@gmx.de> <87zkz9qu2r.fsf@home.jasonrumney.net> <4C0CCBCE.8080503@gmx.de> <87k4qa99l4.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: dough.gmane.org 1275953794 5193 80.91.229.12 (7 Jun 2010 23:36:34 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 7 Jun 2010 23:36:34 +0000 (UTC) Cc: "Stephen J. Turnbull" , Jason Rumney , grischka , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 08 01:36:31 2010 connect(): No such file or directory Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OLlro-0000aY-Rj for ged-emacs-devel@m.gmane.org; Tue, 08 Jun 2010 01:36:29 +0200 Original-Received: from localhost ([127.0.0.1]:35935 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OLlro-0006HE-1d for ged-emacs-devel@m.gmane.org; Mon, 07 Jun 2010 19:36:28 -0400 Original-Received: from [140.186.70.92] (port=53594 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OLlrh-0006GO-3F for emacs-devel@gnu.org; Mon, 07 Jun 2010 19:36:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OLlrf-000194-B0 for emacs-devel@gnu.org; Mon, 07 Jun 2010 19:36:20 -0400 Original-Received: from mail-gw0-f41.google.com ([74.125.83.41]:34572) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OLlrf-00018y-7a; Mon, 07 Jun 2010 19:36:19 -0400 Original-Received: by gwb19 with SMTP id 19so769857gwb.0 for ; Mon, 07 Jun 2010 16:36:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=qpPHFQu37BPOaf64rYrGBKOrY8A7r2UxqNPF2jm85sw=; b=pNobN+8YMMRpMs4V97y3eq3XXWwFeP1mPuYe6Xk4iDuMyt+GNdBAwRdAqWX5f7bOBW brsSdi0sxzKofxNw+JoHiG83cfefRRXDrRFaJhJMYF3besirEaBLikNAmfLMVG20dbT8 97S+rIUukZLpigypEN/srmemeGMtiks0yJu84= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=IWOWpc4gxC7gh0//nqD4Cbvvo0LdDtSTWqa6sBrv7tUMSzMoPHMPt/lUoXIodjzXWu 1dYQfFubBioUSdHAvfBuboTYPuWT6rhd7VAyV2Ft4PEV3F5AuOLlgmdpmQbgipHLSuyo MKR92bzK6pekXdR1lVMcOqmfB5cpT0cm/H5Lg= Original-Received: by 10.101.200.6 with SMTP id c6mr17175071anq.234.1275953778391; Mon, 07 Jun 2010 16:36:18 -0700 (PDT) Original-Received: by 10.100.154.15 with HTTP; Mon, 7 Jun 2010 16:35:58 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:125622 Archived-At: On Mon, Jun 7, 2010 at 9:56 PM, Stefan Monnier wrote: >> threads. And why does not C-g break all looping, even those in timers >> (like fontification)? > > That is simply because timer code is normally run in a way that's > completely hidden from the user, so if the user happens to hit C-g while > a timer is running, it's probably not because he wants to interrupt the > timer, but rather because he wants to interrupt the thing he's > currently doing. Hm, I always hit C-g to interrupt something that Emacs is doing... ;-) How about some convention: Three C-g within three seconds will stop running timers too? > Timers (and fontification, post-command-hook, ...) should run quickly, > or otherwise re-enable interrupts using with-local-quit. Thanks, I see, that is an idea. I had forgotten about it.