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 19:30:15 +0200 Message-ID: References: <4C037EFE.4040304@gmx.de> <87zkz9qu2r.fsf@home.jasonrumney.net> <4C0CCBCE.8080503@gmx.de> <87k4qa99l4.fsf@uwakimon.sk.tsukuba.ac.jp> <4C0D2A87.3070403@gmx.de> 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 1275931849 18634 80.91.229.12 (7 Jun 2010 17:30:49 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 7 Jun 2010 17:30:49 +0000 (UTC) Cc: "Stephen J. Turnbull" , emacs-devel@gnu.org, Jason Rumney To: grischka Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 07 19:30:47 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 1OLg9u-0001mf-Px for ged-emacs-devel@m.gmane.org; Mon, 07 Jun 2010 19:30:47 +0200 Original-Received: from localhost ([127.0.0.1]:45685 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OLg9u-00089U-6v for ged-emacs-devel@m.gmane.org; Mon, 07 Jun 2010 13:30:46 -0400 Original-Received: from [140.186.70.92] (port=57312 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OLg9m-00083b-PH for emacs-devel@gnu.org; Mon, 07 Jun 2010 13:30:41 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OLg9l-0002ca-Ea for emacs-devel@gnu.org; Mon, 07 Jun 2010 13:30:38 -0400 Original-Received: from mail-yw0-f178.google.com ([209.85.211.178]:48426) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OLg9l-0002cL-Av; Mon, 07 Jun 2010 13:30:37 -0400 Original-Received: by ywh8 with SMTP id 8so3251764ywh.6 for ; Mon, 07 Jun 2010 10:30:36 -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=jRuG6bGuVfm0U8OxhxRnpJfY3s4pvh05+nkrEg/lFRE=; b=TVcsHqKuSgwHbuH089kUy+kdMtKdhjlOKRVw41hBa+zYwXLEGp+w3No2XIKV8bnUYm uwxA+Wn+MWHpJ4iVUXPhUZ8bSWsMCCBrQbxdE2gdXZpplQ3A2FRijyTuGeQnymgAEq9X f00C8BCNqLSFrb/7Te5+MhsFpEBRdzcHo/P/U= 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=t3ksctXVPEXczh3TFxh6gxpuZ8fLtVsroz3Yyt39fAObPL66XQ296F65Sq9e0cL/rC s4KYXJ5VLVz4/gDQ8+VqAOoTRgBbFTeFnQU73E8R7BJw0+mQ3ar+21H7XiYdNHQy1vtF CLhzwHPcBdvI8qGIY68iRKYjDTjIfRhj+WLJo= Original-Received: by 10.101.198.23 with SMTP id a23mr15824549anq.231.1275931835977; Mon, 07 Jun 2010 10:30:35 -0700 (PDT) Original-Received: by 10.100.154.15 with HTTP; Mon, 7 Jun 2010 10:30:15 -0700 (PDT) In-Reply-To: <4C0D2A87.3070403@gmx.de> 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:125598 Archived-At: On Mon, Jun 7, 2010 at 7:21 PM, grischka wrote: > Lennart Borgman wrote: >> >> 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.) > > Since this is Emacs you'd probably want to format your status info > in Lisp. =C2=A0Bye nice idea and welcome to thread hell. I see no reason to format it in Lisp. Or rather my idea is that the status information is formated by the lisp thread in advance and sent to the gui thread in a non-lisp format. Then the gui thread can offer that information without contactinog the lisp thread. Displaying that information is just a matter of formatting a native w32 window with it. Similar things can of course be done on other platforms, but this part of the code is necessary platform specif (at least in the core parts of it). > I guess there are some people wondering sometimes about something. > Thread bugs typically show up sometimes. =C2=A0And typically you'll find > nobody who wants to look at them. Looking at this kind of bugs is hard and requires that you have a good enough picture of the message queue system. And just guessing what to look at is difficult.