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: Mon, 7 Jun 2010 17:23:03 +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 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1275925694 24656 80.91.229.12 (7 Jun 2010 15:48:14 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 7 Jun 2010 15:48:14 +0000 (UTC) Cc: grischka , emacs-devel@gnu.org, Jason Rumney To: "Stephen J. Turnbull" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 07 17:48:11 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 1OLeYb-0006Bn-06 for ged-emacs-devel@m.gmane.org; Mon, 07 Jun 2010 17:48:09 +0200 Original-Received: from localhost ([127.0.0.1]:48865 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OLeYa-0001Eq-5b for ged-emacs-devel@m.gmane.org; Mon, 07 Jun 2010 11:48:08 -0400 Original-Received: from [140.186.70.92] (port=49544 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OLeAn-0008AW-Cy for emacs-devel@gnu.org; Mon, 07 Jun 2010 11:23:34 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OLeAh-00044j-66 for emacs-devel@gnu.org; Mon, 07 Jun 2010 11:23:32 -0400 Original-Received: from mail-gw0-f41.google.com ([74.125.83.41]:58376) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OLeAh-00043u-3k; Mon, 07 Jun 2010 11:23:27 -0400 Original-Received: by gwb19 with SMTP id 19so287274gwb.0 for ; Mon, 07 Jun 2010 08:23:23 -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 :content-transfer-encoding; bh=8kThtivIVigl+4oA9uUuQLyyusIynrzCMr0Ugh2FaA0=; b=MUOnMd6585N0LaFP9tdgOW62B0KggEISEGVLVOeOzUxTNL7MreS3jYfaeLC8vdu9jR /ztnDMJv4UmA+z1oT18njo0/KB6BmQjiPlSYwqojUAYGfQt/sFuguwe1cEjDAOXxSF4J 8vSXSxvgTQVIU+YB1elcfeRDnAABXKLHN3BN0= 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:content-transfer-encoding; b=EHCuoBjTsNcaaszoPV0bqhe8n3mIcyfNBMJxKMa38ATOkU0ajbgt66kDLjcAAsPEnA KaK3S8slWNDFR0YXy493tzFekEA9vcdN3DetYdMJHV/yxHAkXYiCh4j0++5ZH3AUteEb XBnMCjwYHBVIG8nzvTXMgx2dtD4Dcbg++ha0c= Original-Received: by 10.101.172.6 with SMTP id z6mr15817474ano.252.1275924203515; Mon, 07 Jun 2010 08:23:23 -0700 (PDT) Original-Received: by 10.100.154.15 with HTTP; Mon, 7 Jun 2010 08:23:03 -0700 (PDT) In-Reply-To: <87k4qa99l4.fsf@uwakimon.sk.tsukuba.ac.jp> 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:125585 Archived-At: On Mon, Jun 7, 2010 at 4:54 PM, Stephen J. Turnbull wr= ote: > grischka writes: > > =C2=A0> XEmacs uses the same thread for lisp and gui and doesn't have any > =C2=A0> such problem. > > XEmacs has such a hairy event loop that it is no longer supported by > X.org. =C2=A0You may not want to go there. > > http://bugs.freedesktop.org/show_bug.cgi?id=3D13471 > https://trac.macports.org/ticket/18491 > http://bugs.freedesktop.org/show_bug.cgi?id=3D20048 ;-) I guess the idea of having two event loops/thread is not in itself bad. If the gui thread is never blocked it can be used to convey status information at least to the user. (You can put these in temporary windows inside the frame for example.) But sometimes I wonder wheter all windows really runs in the gui threads. And why does not C-g break all looping, even those in timers (like fontification)? And is it the same trouble on other platfoms or is it just the w32 port that has this? And moreover I wonder wether all messages really reach their destinations or if something is blocking them in certain situations. (Again, why is not C-g handled in the case above?) And what is blocking Emacs during the time when a new frame is created? Why is not that done asynchronously?