From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: `message' not outputting the newline "atomically" Date: Tue, 09 Jul 2019 18:16:33 +0300 Message-ID: <83imsb5jce.fsf@gnu.org> References: <07619925-e367-fb88-2dd8-27addb2e9052@grinta.net> <68b398b1-3790-b32f-535d-6ea2518f79b8@cs.ucla.edu> <83pnn1lkej.fsf@gnu.org> <83tvccjrpo.fsf@gnu.org> <83zhm3i285.fsf@gnu.org> <7a39d680-6234-1301-74e5-62d599f500f6@cs.ucla.edu> <838stfd0pp.fsf@gnu.org> <835zojd0fx.fsf@gnu.org> <834l43czz8.fsf@gnu.org> <5c979663-9ded-4273-11d1-483345053a6f@cs.ucla.edu> <831rz7cvoh.fsf@gnu.org> <540324b5-fad3-ded0-5018-6abb494ce126@cs.ucla.edu> <83blyaaq5l.fsf@gnu.org> <73e8afc0-2151-9c8b-26c5-454fcd2f361d@cs.ucla.edu> <83tvbx7v9l.fsf@gnu.org> <83v9wc543f.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="50679"; mail-complaints-to="usenet@blaine.gmane.org" Cc: larsi@gnus.org, eggert@cs.ucla.edu, daniele@grinta.net, emacs-devel@gnu.org To: Richard Copley Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jul 09 17:32:34 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hks6b-000CKS-PQ for ged-emacs-devel@m.gmane.org; Tue, 09 Jul 2019 17:32:33 +0200 Original-Received: from localhost ([::1]:50944 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hkrrU-0005yE-6u for ged-emacs-devel@m.gmane.org; Tue, 09 Jul 2019 11:16:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41873) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hkrrO-0005xu-DU for emacs-devel@gnu.org; Tue, 09 Jul 2019 11:16:52 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52383) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hkrrN-0004Nl-Pn; Tue, 09 Jul 2019 11:16:49 -0400 Original-Received: from [176.228.60.248] (port=4590 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hkrrM-0002TN-Ii; Tue, 09 Jul 2019 11:16:49 -0400 In-reply-to: (message from Richard Copley on Tue, 9 Jul 2019 14:45:58 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:238453 Archived-At: > From: Richard Copley > Date: Tue, 9 Jul 2019 14:45:58 +0100 > Cc: Paul Eggert , Lars Magne Ingebrigtsen , daniele@grinta.net, > Emacs Development > > > "make -O=line" buffers all output from one line of the Makefile. > > For typical targets with only one command, it's the same as "-O". > > Our targets are not one-line, though. > > Some are, notably .c.o. Which is fine, because people who use this option don't want diagnostics from different source files mixed up. > The point is that your statement that "make -O=line" > "provides the line-level separation that you want to see" is not true. It's up to > you to decide if that affects your argument. Whether to use that option is in the eyes of the beholder, of course. Exactly like any other Make option, like -jN. It comes for a price, but whether one is prepared to pay that price is up to each one of us, and depends on what we want to do.