From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: async-shell-command and prefix argument Date: Sun, 20 Jan 2019 05:40:04 +0200 Message-ID: <83a7jwatez.fsf@gnu.org> References: <87bm4jnevo.fsf@mbork.pl> <83zhs1ddxw.fsf@gnu.org> <871s5dt3cj.fsf@mbork.pl> <87won0fia8.fsf@mail.linkov.net> NNTP-Posting-Host: ciao.gmane.org X-Trace: ciao.gmane.org 1547955626 14559 195.159.176.228 (20 Jan 2019 03:40:26 GMT) X-Complaints-To: usenet@ciao.gmane.org NNTP-Posting-Date: Sun, 20 Jan 2019 03:40:26 +0000 (UTC) Cc: emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 20 04:40:24 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1gl3yC-0003mM-Aa for ged-emacs-devel@m.gmane.org; Sun, 20 Jan 2019 04:40:24 +0100 Original-Received: from localhost ([127.0.0.1]:34846 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gl3yH-000205-Us for ged-emacs-devel@m.gmane.org; Sat, 19 Jan 2019 22:40:32 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:38210) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gl3yC-0001zy-IX for emacs-devel@gnu.org; Sat, 19 Jan 2019 22:40:25 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:42989) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gl3yB-0005ju-BJ; Sat, 19 Jan 2019 22:40:23 -0500 Original-Received: from [176.228.60.248] (port=4984 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gl3yA-00077t-Rl; Sat, 19 Jan 2019 22:40:23 -0500 In-reply-to: <87won0fia8.fsf@mail.linkov.net> (message from Juri Linkov on Sat, 19 Jan 2019 23:19:19 +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:232523 Archived-At: > From: Juri Linkov > Date: Sat, 19 Jan 2019 23:19:19 +0200 > Cc: Eli Zaretskii , emacs-devel@gnu.org > > >> Is something wrong with customizing async-shell-command-display-buffer? > >> I have it set to nil for quite some time. > > > > Would it help for this use-case? That is, make the output buffers > > disappear (even in the presence of some output), but not if a prefix > > argument is used? > > Does C-u already mean inserting the output in the current buffer? > Maybe then you could use e.g. M-0 prefix arg? We already have async-shell-command-display-buffer, which can be customized to makes the buffer appear only if it has something in it. Why is that not enough? Is the case where the user decides up front she doesn't want to see the buffer, ever, no matter what's in it, an important enough use case? And if it is, why a new value of async-shell-command-display-buffer couldn't cater even to that weird use case?