From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#18133: Suppressing asynchronous command output Date: Sat, 24 Dec 2016 18:03:06 +0200 Message-ID: <83zijlxqkl.fsf@gnu.org> References: <83zijp180n.fsf@gnu.org> <83eg100vy5.fsf@gnu.org> <585C132B.1030709@gmx.at> <585C347D.9050309@gmx.at> <585D740B.40303@gmx.at> <585D8120.1090300@gmx.at> <585E3CF2.4070800@gmx.at> <837f6pzg2s.fsf@gnu.org> <585E7DF8.30205@gmx.at> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1482595459 31557 195.159.176.226 (24 Dec 2016 16:04:19 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 24 Dec 2016 16:04:19 +0000 (UTC) Cc: 18133@debbugs.gnu.org, rrt@sc3d.org To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Dec 24 17:04:13 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 1cKonp-0006yl-1v for geb-bug-gnu-emacs@m.gmane.org; Sat, 24 Dec 2016 17:04:09 +0100 Original-Received: from localhost ([::1]:44003 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cKont-0006fw-O1 for geb-bug-gnu-emacs@m.gmane.org; Sat, 24 Dec 2016 11:04:13 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52018) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cKonm-0006f7-Pt for bug-gnu-emacs@gnu.org; Sat, 24 Dec 2016 11:04:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cKoni-0006ed-8b for bug-gnu-emacs@gnu.org; Sat, 24 Dec 2016 11:04:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:38501) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cKoni-0006eT-5i for bug-gnu-emacs@gnu.org; Sat, 24 Dec 2016 11:04:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cKonh-0000wh-SI for bug-gnu-emacs@gnu.org; Sat, 24 Dec 2016 11:04:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 24 Dec 2016 16:04: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.14825954303614 (code B ref 18133); Sat, 24 Dec 2016 16:04:01 +0000 Original-Received: (at 18133) by debbugs.gnu.org; 24 Dec 2016 16:03:50 +0000 Original-Received: from localhost ([127.0.0.1]:53900 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cKonV-0000wD-GT for submit@debbugs.gnu.org; Sat, 24 Dec 2016 11:03:50 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:60866) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cKonT-0000vz-HR for 18133@debbugs.gnu.org; Sat, 24 Dec 2016 11:03:47 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cKonJ-0006Eq-5K for 18133@debbugs.gnu.org; Sat, 24 Dec 2016 11:03:42 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:49993) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cKonJ-0006Eg-1R; Sat, 24 Dec 2016 11:03:37 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4066 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cKonG-0007La-8r; Sat, 24 Dec 2016 11:03:36 -0500 In-reply-to: <585E7DF8.30205@gmx.at> (message from martin rudalics on Sat, 24 Dec 2016 14:54:00 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:127401 Archived-At: > Date: Sat, 24 Dec 2016 14:54:00 +0100 > From: martin rudalics > CC: 18133@debbugs.gnu.org > > > display-buffer-alist is a defcustom. The issue at hand is to offer > > users a way of customizing display-buffer-alist such that buffers > > whose names match "*Async Shell Command*" will not be displayed unless > > they have something to show the user. > > > > Martin, what can we add to the display-buffer-alist's defcustom to > > allow users easy customization to that effect? > > Let me try to explain this once more: The idea of ‘display-buffer-alist’ > was to provide an option with a default value of nil. An option > entirely in the hands of the user, which means that no code is allowed > to change its value. In the five years since its introduction, new > Emacs code has followed this convention. I'm not talking about any code that would change the default value. I'm talking about showing the users a non-default value, for them to select if they want to, that would produce the effect desired here. IOW, when the user clicks "Value menu", I would like them to see a value which makes async shell buffers behave like Reuben wants. That's all. If you are saying that we must not show any value but nil in the value menu, then my next question will be why is this variable a defcustom, if users are not allowed to select non-default values for it. > Applications have three ways to affect what ‘display-buffer’ does: We are not talking about any applications, at least I wasn't. I was talking about providing another possible value, that'd be easy to select without writing any Lisp, and which, when selected, will cause the async shell output buffer be displayed only when there's some material in it. > Is it really so difficult to provide an extra option which allows to > have either of these trigger the wanted behavior? Also taking into > account that the lazy pop-up behavior Reuben aims at cannot be obtained > by customizing an existing option anyway? AFAIU, customizing display-buffer-alist, an existing option, does in fact produce the desired effect.