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: Sat, 22 Jun 2019 22:00:25 +0300 Message-ID: <83zhm9momu.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> <83o92rpk1g.fsf@gnu.org> <9d07a8e2-7f9b-bbfa-b73e-0d7aee09b099@cs.ucla.edu> <5a3dfa65-a394-19d5-54a1-4a8bd63693e6@cs.ucla.edu> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="136712"; 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 Sat Jun 22 21:02:27 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 1helHP-000ZQa-3R for ged-emacs-devel@m.gmane.org; Sat, 22 Jun 2019 21:02:27 +0200 Original-Received: from localhost ([::1]:42100 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1helHO-0000W0-5a for ged-emacs-devel@m.gmane.org; Sat, 22 Jun 2019 15:02:26 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45493) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1helFj-0000HW-Gg for emacs-devel@gnu.org; Sat, 22 Jun 2019 15:00:49 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:36900) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1helFa-00056b-QX; Sat, 22 Jun 2019 15:00:36 -0400 Original-Received: from [176.228.60.248] (port=3449 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1helFZ-0002v3-M1; Sat, 22 Jun 2019 15:00:34 -0400 In-reply-to: <5a3dfa65-a394-19d5-54a1-4a8bd63693e6@cs.ucla.edu> (message from Paul Eggert on Sat, 22 Jun 2019 11:53:36 -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:238043 Archived-At: > From: Paul Eggert > Date: Sat, 22 Jun 2019 11:53:36 -0700 > Cc: Eli Zaretskii , larsi@gnus.org, emacs-devel@gnu.org > > Andreas Schwab wrote: > > On Jun 21 2019, Paul Eggert wrote: > > > >> it'll mess up formatting for the next stderr diagnostic, and (c) POSIX > >> allows platforms to line-buffer stderr by default and Emacs has been > >> working on such platforms for ages anyway. > > > > How do you know? > > Trivially, by using a recent Emacs master on GNU/Linux, as this uses > line-buffered stderr. It works fine. That's not "for ages", though, is it?