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: Fri, 21 Jun 2019 08:46:51 +0300 Message-ID: <83o92rpk1g.fsf@gnu.org> References: <83y31xr3aa.fsf@gnu.org> <26154872-1a5c-7302-0f32-b16aff8e0ae7@cs.ucla.edu> <83blytq90m.fsf@gnu.org> <95de57fb-ef8c-a65f-d3ca-4a9e7f0f38bc@cs.ucla.edu> <83a7ecquzb.fsf@gnu.org> <83tvckp5ni.fsf@gnu.org> <83r27op1wb.fsf@gnu.org> <60d1b05d-ef4c-252a-0626-8c69c103fdf0@cs.ucla.edu> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="230612"; mail-complaints-to="usenet@blaine.gmane.org" Cc: schwab@suse.de, larsi@gnus.org, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 21 07:47:15 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 1heCOJ-000xse-3b for ged-emacs-devel@m.gmane.org; Fri, 21 Jun 2019 07:47:15 +0200 Original-Received: from localhost ([::1]:54892 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1heCOH-0006ms-4p for ged-emacs-devel@m.gmane.org; Fri, 21 Jun 2019 01:47:13 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39171) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1heCOA-0006mZ-Uh for emacs-devel@gnu.org; Fri, 21 Jun 2019 01:47:08 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46196) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1heCO7-0006RJ-FD; Fri, 21 Jun 2019 01:47:04 -0400 Original-Received: from [176.228.60.248] (port=4118 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1heCO6-0006tV-1m; Fri, 21 Jun 2019 01:47:03 -0400 In-reply-to: <60d1b05d-ef4c-252a-0626-8c69c103fdf0@cs.ucla.edu> (message from Paul Eggert on Thu, 20 Jun 2019 12:33:13 -0700) 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:237993 Archived-At: > Cc: schwab@suse.de, larsi@gnus.org, emacs-devel@gnu.org > From: Paul Eggert > Date: Thu, 20 Jun 2019 12:33:13 -0700 > > > I think we do want it to be unbuffered, so that important error > > messages are output in their entirety, or as close as possible. > Every important Emacs stderr message ends in newline So now we will have to enforce this all over the place, in order to ensure that critical messages get through? Just to placate the situation with interleaving output from two or more instances of Emacs? Like I said, on balance this is a bad change. It may or may not make a significant difference on GNU/Linux, but there are other systems out there. And even on GNU/Linux, we have no control on what the glibc developers may decide about this tomorrow, given the lax Posix requirements.