From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Inhibit "Wrote foo" from write-region Date: Thu, 23 Jan 2014 20:07:21 +0200 Message-ID: <83mwimefmu.fsf@gnu.org> References: <87k3dte17j.fsf@fleche.redhat.com> <83siseekd4.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1390500434 6184 80.91.229.3 (23 Jan 2014 18:07:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 23 Jan 2014 18:07:14 +0000 (UTC) Cc: tromey@redhat.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Sebastian Wiesner Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 23 19:07:20 2014 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 1W6OgS-0000Mu-5e for ged-emacs-devel@m.gmane.org; Thu, 23 Jan 2014 19:07:20 +0100 Original-Received: from localhost ([::1]:42633 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6OgR-0006d8-Ix for ged-emacs-devel@m.gmane.org; Thu, 23 Jan 2014 13:07:19 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54229) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6OgK-0006c8-31 for emacs-devel@gnu.org; Thu, 23 Jan 2014 13:07:18 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W6OgD-0002cg-NM for emacs-devel@gnu.org; Thu, 23 Jan 2014 13:07:12 -0500 Original-Received: from mtaout29.012.net.il ([80.179.55.185]:47559) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W6OgD-0002bI-Ft for emacs-devel@gnu.org; Thu, 23 Jan 2014 13:07:05 -0500 Original-Received: from conversion-daemon.mtaout29.012.net.il by mtaout29.012.net.il (HyperSendmail v2007.08) id <0MZV00M008LMNA00@mtaout29.012.net.il> for emacs-devel@gnu.org; Thu, 23 Jan 2014 20:08:20 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout29.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MZV00LEO91VCT30@mtaout29.012.net.il>; Thu, 23 Jan 2014 20:08:20 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.185 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:168972 Archived-At: > Date: Thu, 23 Jan 2014 18:37:09 +0100 > From: Sebastian Wiesner > Cc: tromey@redhat.com, emacs-devel@gnu.org, > Stefan Monnier > > > I, for one, am accustomed to see these messages while Emacs is being > > built: in a highly parallel build that is sometimes the only practical > > way of knowing whether some part of the build succeeded or not. > > How do you do that?! Do you really read *all* messages being printed while > building?! When I need to understand what went wrong, I read many of them, yes. > I presume that just testing for the existence of interesting files (e.g. > good old "find") isn't an option? With today's fast machines, that's not good enough: it's not easy to be sure whether a given file was created by this or the previous build, when you run one after the other (perhaps trying to fix a problem). > Isn't that the job of the build system rather? When the build system becomes smart enough to tell me what went wrong, I will no longer need this, indeed.