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: Wed, 26 Jun 2019 22:11:42 +0300 Message-ID: <83a7e4jh5d.fsf@gnu.org> References: <07619925-e367-fb88-2dd8-27addb2e9052@grinta.net> <68b398b1-3790-b32f-535d-6ea2518f79b8@cs.ucla.edu> <83r27hlkix.fsf@gnu.org> <1d550142-8d66-485b-6796-981351718b53@cs.ucla.edu> <83blykjijy.fsf@gnu.org> <65c60a70-311d-bf9f-b509-d3dd80ddc511@cs.ucla.edu> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="99915"; mail-complaints-to="usenet@blaine.gmane.org" Cc: larsi@gnus.org, daniele@grinta.net, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 26 21:12:56 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 1hgDLi-000Prq-DO for ged-emacs-devel@m.gmane.org; Wed, 26 Jun 2019 21:12:54 +0200 Original-Received: from localhost ([::1]:44456 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hgDLh-0005bb-Bh for ged-emacs-devel@m.gmane.org; Wed, 26 Jun 2019 15:12:53 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53205) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hgDKv-0005bU-J5 for emacs-devel@gnu.org; Wed, 26 Jun 2019 15:12:06 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:59017) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hgDKu-00049p-Bk; Wed, 26 Jun 2019 15:12:04 -0400 Original-Received: from [176.228.60.248] (port=1513 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hgDKt-0005ts-4Y; Wed, 26 Jun 2019 15:12:04 -0400 In-reply-to: <65c60a70-311d-bf9f-b509-d3dd80ddc511@cs.ucla.edu> (message from Paul Eggert on Wed, 26 Jun 2019 11:58:26 -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:238177 Archived-At: > Cc: larsi@gnus.org, daniele@grinta.net, emacs-devel@gnu.org > From: Paul Eggert > Date: Wed, 26 Jun 2019 11:58:26 -0700 > > Emacs contains many fprintf calls like this: > > fprintf (stderr, "Using %s\n", term); > > Here, TERM is typically a short string. On AIX and Solaris, this fprintf is > implemented via three 'write' syscalls - one for "Using ", one for the contents > of TERM, and one for "\n". These outputs will be broken up and hard-to-read on > AIX and Solaris, if Emacs runs in parallel with other programs also generating > stderr output. Using line-buffering fixes this. Can't we also fix that by replacing the above with 'sprintf' followed by 'write'? Or some other similar solution?