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: [PATCH 2/3] Don't print "process finished" into the stderr buffer. Date: Sat, 20 Apr 2019 10:30:59 +0300 Message-ID: <83imv9b0b0.fsf@gnu.org> References: <20180404120218.257212-1-phst@google.com> <20180404120218.257212-2-phst@google.com> <834lkr3ygo.fsf@gnu.org> <83lgdxzvs2.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="5967"; mail-complaints-to="usenet@blaine.gmane.org" Cc: phst@google.com, emacs-devel@gnu.org To: Philipp Stephani Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Apr 20 09:31:25 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.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hHkT6-0001RM-Be for ged-emacs-devel@m.gmane.org; Sat, 20 Apr 2019 09:31:24 +0200 Original-Received: from localhost ([127.0.0.1]:38015 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hHkT5-0007VA-Bc for ged-emacs-devel@m.gmane.org; Sat, 20 Apr 2019 03:31:23 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:39419) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hHkSy-0007V5-Cz for emacs-devel@gnu.org; Sat, 20 Apr 2019 03:31:17 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:56382) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hHkSy-00051P-0h; Sat, 20 Apr 2019 03:31:16 -0400 Original-Received: from [176.228.60.248] (port=4094 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hHkSx-0001UZ-6i; Sat, 20 Apr 2019 03:31:15 -0400 In-reply-to: (message from Philipp Stephani on Fri, 19 Apr 2019 21:28:32 +0200) 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.21 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:235690 Archived-At: > From: Philipp Stephani > Date: Fri, 19 Apr 2019 21:28:32 +0200 > Cc: Emacs developers , Philipp Stephani > > > But I'm guessing that the current behavior was unexpected for some > > reason, and that's why you looked in the documentation. If the guess > > is correct, could you describe why it was unexpected/unwanted? > > It's unexpected that Emacs writes something. This is an instance of > the general case that by default you expect nothing to happen instead > of something, unless you request the "something". For example, after > $ echo foo > bar > would you expect that the file "bar" contains content other than > "foo\n" because the shell decides to write additional text before > closing redirections? This is the same thing. But Emacs does that for ages, so in Emacs this is veteran behavior of the default sentinel function. > The documentation for make-process doesn't state that if :stderr is a > buffer, make-process creates a pipe process with the default sentinel; Actually, it does, albeit in the parent section: Alternatively, you could use the ‘:stderr’ parameter with a non-‘nil’ value in a call to ‘make-process’ (*note make-process: Asynchronous Processes.) to make the destination of the error output separate from the standard output; in that case, Emacs will use pipes for communicating with the subprocess.