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: Thu, 22 Dec 2016 20:26:40 +0000 Message-ID: References: <83zijp180n.fsf@gnu.org> <83eg100vy5.fsf@gnu.org> <585C132B.1030709@gmx.at> <585C347D.9050309@gmx.at> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1135da064b59110544451661 X-Trace: blaine.gmane.org 1482438435 32292 195.159.176.226 (22 Dec 2016 20:27:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 22 Dec 2016 20:27:15 +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 Thu Dec 22 21:27:10 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 1cK9xD-0007T8-JT for geb-bug-gnu-emacs@m.gmane.org; Thu, 22 Dec 2016 21:27:07 +0100 Original-Received: from localhost ([::1]:36107 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cK9xI-0000Wr-3b for geb-bug-gnu-emacs@m.gmane.org; Thu, 22 Dec 2016 15:27:12 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40101) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cK9xB-0000Wa-ES for bug-gnu-emacs@gnu.org; Thu, 22 Dec 2016 15:27:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cK9x8-0004wm-8O for bug-gnu-emacs@gnu.org; Thu, 22 Dec 2016 15:27:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:36492) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cK9x8-0004wb-4s for bug-gnu-emacs@gnu.org; Thu, 22 Dec 2016 15:27:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cK9x7-0006FV-TB for bug-gnu-emacs@gnu.org; Thu, 22 Dec 2016 15:27:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Reuben Thomas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 22 Dec 2016 20:27:01 +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.148243840823998 (code B ref 18133); Thu, 22 Dec 2016 20:27:01 +0000 Original-Received: (at 18133) by debbugs.gnu.org; 22 Dec 2016 20:26:48 +0000 Original-Received: from localhost ([127.0.0.1]:51891 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cK9wt-0006Ez-QO for submit@debbugs.gnu.org; Thu, 22 Dec 2016 15:26:48 -0500 Original-Received: from mail-qt0-f172.google.com ([209.85.216.172]:35969) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cK9ws-0006Ej-KK for 18133@debbugs.gnu.org; Thu, 22 Dec 2016 15:26:47 -0500 Original-Received: by mail-qt0-f172.google.com with SMTP id k15so5357626qtg.3 for <18133@debbugs.gnu.org>; Thu, 22 Dec 2016 12:26:46 -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=mUu/eDvcrl8ZwhiOuoVaF8nJulW6U0yryFqoENdlvck=; b=u9Y0pJtDascMMqm49nFZ2E/bPcOk14c5c9sFgrGWCsiyE+h+1Z9F57EcTlBE3FZEZo /vB1VEd6sLxhzUFEO3F7IhVXRf/UgIBdGjEUwmfTq0F3FYzdPA0ib63NqFjdYjM6abyA EnQZTvFt57bayg21DxMX3PU3vDxTUjOFxBVqE= 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=mUu/eDvcrl8ZwhiOuoVaF8nJulW6U0yryFqoENdlvck=; b=BTaF9DywM9kjUadqfVMSIOqoiSzKQXWz4MLyjUQVOZ/nzQFIq9S8cSIegO5jVhgXdb XecCRyuiBqwtIAiHW5icNFz5BGZkuxNANBYToJ9Zvc07BpaY55A85sMpnjc8qawfXW4n 3iC7TEIl9nKfiURp8hC0pF7HomXFoPxvyPdnQv0fV/9xOULKuCDc7OnXhSddU52/ONXl OOXIqQjHr0I1a5kcAJq00qTMK5Mu6EZjNZZVtGMuoll+TAQSJaiEOuNyjsRRu7bEsV4t T7cmrp/gNMVsMZTN3RpNIUBGUFtzF0ooqYOfz+oCLjUVg3mxIrv1v1BEyQa8wMMcQ85i lJjQ== X-Gm-Message-State: AIkVDXIZo7WS0JrxLOeO6SxAVDDvRwXYVpgD+6S1b2ulParfF9ZITfUo43JFqXQg76+9biNCpM+h3mmAeyejSOgp X-Received: by 10.200.47.38 with SMTP id j35mr11622706qta.136.1482438401007; Thu, 22 Dec 2016 12:26:41 -0800 (PST) Original-Received: by 10.140.88.51 with HTTP; Thu, 22 Dec 2016 12:26:40 -0800 (PST) In-Reply-To: <585C347D.9050309@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:127343 Archived-At: --001a1135da064b59110544451661 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 22 December 2016 at 20:15, martin rudalics wrote: > > =E2=80=8BI meant the second, just adding the (buffer-name-string . > > display-buffer-no-window) pair to the value menu. > > Which value menu? =E2=80=98display-buffer-alist=E2=80=99 is a user optio= n - its > original value must be nil, no code is allowed to add anything to it. > =E2=80=8BThat's what I meant, so I guess it will have to be something else.= =E2=80=8B If an application urgently wants to override the user, it can use > =E2=80=98display-buffer-overriding-action=E2=80=99. > =E2=80=8BI'm not trying to override the user here, I'm just trying to avoid= adding another configuration option.=E2=80=8B But even if it were a configuration option, if code can't add anything to display-buffer-alist, then how should this setting be implemented? (As you can see, the current implementation relies on changing display-buffer-alist.) I'm a bit confused, how is display-buffer-alist different from, say, auto-mode-alist (which can be altered by the user, but also is added to by code.) Or do you just want to add =E2=80=98display-buffer-no-window=E2=80=99 to > =E2=80=98display-buffer--action-function-custom-type=E2=80=99? > It would be nice if the user only had to change one thing to enable hiding the async output buffer until there is output. If we only added the function to display-buffer--action-function-custom-type, the user still has to manually add the right buffer name pattern and the action to display-buffer-alist. --=20 http://rrt.sc3d.org --001a1135da064b59110544451661 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On = 22 December 2016 at 20:15, martin rudalics <rudalics@gmx.at> w= rote:
> =E2=80=8BI meant the second,= just adding the (buffer-name-string .
> display-buffer-no-window) pair to the value menu.

 Which value menu?=C2=A0 =E2=80=98display-buffer-alist=E2=80=99 is a user op= tion - its
original value must be nil, no code is allowed to add anything to it.

=E2=80=8BThat's what I meant, so I guess it will have to be = something else.=E2=80=8B

If an application urgently wants to override the user, it can use
=E2=80=98display-buffer-overriding-action=E2=80=99.

= =E2=80=8BI'm not trying to override the user here, I'm just trying = to avoid adding another configuration option.=E2=80=8B

But even if it were a configuration opt= ion, if code can't add anything to display-buffer-alist, then how shoul= d this setting be implemented? (As you can see, the current implementation = relies on changing display-buffer-alist.) I'm a bit confused, how is di= splay-buffer-alist different from, say, auto-mode-alist (which can be alter= ed by the user, but also is added to by code.)

Or do you just want to add =E2=80=98display-buffer-n= o-window=E2=80=99 to
=E2=80=98display-buffer--action-function-custom-type=E2=80=99?

It would be nice if the user only had to change one thing= to enable hiding the async output buffer until there is output. If we only= added the function to display-buffer--action-function-custom-type, the use= r still has to manually add the right buffer name pattern and the action to= display-buffer-alist.

--
http://rrt.sc3d.org
--001a1135da064b59110544451661--