From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Reuben Thomas Newsgroups: gmane.emacs.bugs Subject: bug#18133: Suppressing asynchronous command output Date: Fri, 23 Dec 2016 19:10:01 +0000 Message-ID: References: <83zijp180n.fsf@gnu.org> <83eg100vy5.fsf@gnu.org> <585C132B.1030709@gmx.at> <585C347D.9050309@gmx.at> <585D740B.40303@gmx.at> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c05a830fd760c054458216e X-Trace: blaine.gmane.org 1482520281 23534 195.159.176.226 (23 Dec 2016 19:11:21 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 23 Dec 2016 19:11:21 +0000 (UTC) Cc: 18133@debbugs.gnu.org To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Dec 23 20:11:15 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cKVFD-0004Z3-Sv for geb-bug-gnu-emacs@m.gmane.org; Fri, 23 Dec 2016 20:11:08 +0100 Original-Received: from localhost ([::1]:40508 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cKVFI-0006kt-Ga for geb-bug-gnu-emacs@m.gmane.org; Fri, 23 Dec 2016 14:11:12 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50550) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cKVFB-0006km-QR for bug-gnu-emacs@gnu.org; Fri, 23 Dec 2016 14:11:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cKVF8-0005Dh-Jp for bug-gnu-emacs@gnu.org; Fri, 23 Dec 2016 14:11:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:37571) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cKVF8-0005DZ-G4 for bug-gnu-emacs@gnu.org; Fri, 23 Dec 2016 14:11:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cKVF8-0000Jh-8p for bug-gnu-emacs@gnu.org; Fri, 23 Dec 2016 14:11:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Reuben Thomas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 23 Dec 2016 19:11:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 18133 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 18133-submit@debbugs.gnu.org id=B18133.14825202101146 (code B ref 18133); Fri, 23 Dec 2016 19:11:02 +0000 Original-Received: (at 18133) by debbugs.gnu.org; 23 Dec 2016 19:10:10 +0000 Original-Received: from localhost ([127.0.0.1]:52970 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cKVEH-0000IQ-LW for submit@debbugs.gnu.org; Fri, 23 Dec 2016 14:10:10 -0500 Original-Received: from mail-qk0-f179.google.com ([209.85.220.179]:33130) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cKVEF-0000IA-Ap for 18133@debbugs.gnu.org; Fri, 23 Dec 2016 14:10:07 -0500 Original-Received: by mail-qk0-f179.google.com with SMTP id t184so151485800qkd.0 for <18133@debbugs.gnu.org>; Fri, 23 Dec 2016 11:10:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sc3d.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tOxHWWSMnl22Hj0jc87yLi7MP9im4Y0PfR3gK0u7Oi8=; b=rp5juXUe6FlEY90FEgKUEBV9OKhnhv9i7wlhYyrl3/vq91ijBA5xb/XF5gfBHkRywP myRZez1NspKPVOmvu0JH4HNuRlrX5mi89sNK9BsONgnf0T7Q4AlEGtUbRhtuuos+SOIG Kh5kCmPks9lAqWcrDAvB2yheOuwQ2EgRy/KeY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tOxHWWSMnl22Hj0jc87yLi7MP9im4Y0PfR3gK0u7Oi8=; b=Qa/66HeRxYQss/vO/qCK1kJrKORX7IV5fajdtJ9zBFY8k/9NpX4ctxLlxw2MHa1Yx9 SQSYzSX9wSX20ZROIjUb3XwYYaa+Q2hZIPU707QEA8ZX6RPyDQsTmYFc6LwGWEti2ZyW lreJqdqivwGy4oxhZvlV8Qbr0Dx7Vw4S/rLvM/wGqJ1ipBq/sHsK+VSIeYGFoXrq2dTI /laihH97detvTOdSKeq4ljPzDo3nQWU3w5UXv4XvxM2uwhzX9yfXjXlUrsFhSp4XA37b bJWjqzblrjDglSFl22/KhRVa5n2moFGDO7Xmt0MG+rF7zxJswxmFzu+9O+lJIeh6uYxi nGUQ== X-Gm-Message-State: AIkVDXIWmwR/ApAeTQV1oDcQ0zxdiXsLgElytLj62S25T8mzXlAUaArAFpCvrcHBzIhZ8KEoGV0EHikPv9mboLKI X-Received: by 10.55.113.69 with SMTP id m66mr15985388qkc.186.1482520201605; Fri, 23 Dec 2016 11:10:01 -0800 (PST) Original-Received: by 10.140.88.51 with HTTP; Fri, 23 Dec 2016 11:10:01 -0800 (PST) In-Reply-To: <585D740B.40303@gmx.at> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:127377 Archived-At: --94eb2c05a830fd760c054458216e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 23 December 2016 at 18:59, martin rudalics wrote: > > =E2=80=8BI'm not trying to override the user here, I'm just trying to a= void > adding > > another configuration option.=E2=80=8B > > You change long-standing behavior when you add such an option. =E2=80=8BI haven't talked about adding an option.=E2=80=8B > Did > =E2=80=8B p=E2=80=8B > eople agree that the buffer should be preferably not displayed? The > current status is that > > To run COMMAND without displaying the output > in a window you can configure `display-buffer-alist' to use the action > `display-buffer-no-window' for the buffer `*Async Shell Command*'. > > With your proposal the buffer would not be displayed and the user would > have to delete the =E2=80=98display-buffer-alist=E2=80=99 entry to displa= y the buffer. > =E2=80=8BThat's the case with my original patch. But I agreed with Eli (and= you) that the default behaviour should be the same as at present.=E2=80=8B =E2=80=8BI'm just asking how to implement this, preferably without adding a= nother configuration option.=E2=80=8B > > It would be nice if the user only had to change one thing to enable > hiding > > the async output buffer until there is output. > > But when you add the entry to =E2=80=98display-buffer-alist=E2=80=99 the = buffer will > already be hidden without any user intervention. =E2=80=8BAgain, you are describing the behaviour of my original patch. =E2= =80=8BI then suggested adding an option to display-buffer-alist's defcustom specification. But you said that is not allowed (if I understood correctly)= . I will try to outline the current position again: 1. I agree that the current default behaviour should remain as it is. 2. I would like to add the ability to easily turn off displaying the Async Command output buffer until there is some output. 3. I suggested achieving this by i) adding an option to display-buffer-alist, and ii) documenting this in shell-command. 4. You stated that it is not allowed for code to change display-buffer-alist. I was puzzled by this, because other user variables such as auto-mode-alist are changed by code as well as by the user. In any case, I am not suggesting automatically changing display-buffer-alist; rather I have suggested adding an option to the customization menu for display-buffer-alist. So, maybe you could give your opinion of my current suggestion (3), ignoring my original patch? Sorry if I have confused you, and I hope the above makes things clearer. --=20 http://rrt.sc3d.org --94eb2c05a830fd760c054458216e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On = 23 December 2016 at 18:59, martin rudalics <rudalics@gmx.at> w= rote:
> =E2=80=8BI'm not trying = to override the user here, I'm just trying to avoid adding
> another configuration option.=E2=80=8B

 You change long-standing behavior when you add such an option.=

= =E2=80=8BI haven't talked about adding an option.=E2=80=8B
<= div>=C2=A0
Did
=E2=80=8B p= =E2=80=8B
eople agree that the buffer should be preferably not display= ed?=C2=A0 The
current status is that

=C2=A0 To run COMMAND without displaying the output
=C2=A0 in a window you can configure `display-buffer-alist' to use the = action
=C2=A0 `display-buffer-no-window' for the buffer `*Async Shell Command*= '.

With your proposal the buffer would not be displayed and the user would
have to delete the =E2=80=98display-buffer-alist=E2=80=99 entry to display = the buffer.

=E2=80=8BThat's the case with my original p= atch. But I agreed with Eli (and you) that the default behaviour should be = the same as at present.=E2=80=8B

=E2=80=8BI'm just asking how to implem= ent this, preferably without adding another configuration option.=E2=80=8B<= /div>
=C2=A0
> It would be nice if the user only had to change on= e thing to enable hiding
> the async output buffer until there is output.

 But when you add the entry to =E2=80=98display-buffer-alist=E2=80=99 the bu= ffer will
already be hidden without any user intervention.

=E2=80=8BAgain= , you are describing the behaviour of my original patch. =E2=80=8BI then su= ggested adding an option to display-buffer-alist's defcustom specificat= ion. But you said that is not allowed (if I understood correctly).

I will try to outline the c= urrent position again:

1.= I agree that the current default behaviour should remain as it is.

2. I would like to add the abi= lity to easily turn off displaying the Async Command output buffer until th= ere is some output.

3. I = suggested achieving this by i) adding an option to display-buffer-alist, an= d ii) documenting this in shell-command.

4. You stated that it is not allowed for code to change dis= play-buffer-alist. I was puzzled by this, because other user variables such= as auto-mode-alist are changed by code as well as by the user. In any case= , I am not suggesting automatically changing display-buffer-alist; rather I= have suggested adding an option to the customization menu for display-buff= er-alist.

<= /div>
So, maybe you c= ould give your opinion of my current suggestion (3), ignoring my original p= atch?

Sorry if I have con= fused you, and I hope the above makes things clearer.
--94eb2c05a830fd760c054458216e--