From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#18133: Suppressing asynchronous command output Date: Sat, 24 Dec 2016 19:14:56 +0100 Message-ID: <585EBB20.7040302@gmx.at> 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> <83zijlxqkl.fsf@gnu.org> <585EA33D.5010904@gmx.at> <83tw9txo31.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1482603373 28194 195.159.176.226 (24 Dec 2016 18:16:13 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 24 Dec 2016 18:16:13 +0000 (UTC) Cc: 18133@debbugs.gnu.org, rrt@sc3d.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Dec 24 19:16:09 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 1cKqrY-0006hG-C2 for geb-bug-gnu-emacs@m.gmane.org; Sat, 24 Dec 2016 19:16:08 +0100 Original-Received: from localhost ([::1]:44438 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cKqrd-0002hp-3E for geb-bug-gnu-emacs@m.gmane.org; Sat, 24 Dec 2016 13:16:13 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47775) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cKqrV-0002hk-Kk for bug-gnu-emacs@gnu.org; Sat, 24 Dec 2016 13:16:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cKqrS-0000jS-CJ for bug-gnu-emacs@gnu.org; Sat, 24 Dec 2016 13:16:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:38605) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cKqrS-0000jO-8j for bug-gnu-emacs@gnu.org; Sat, 24 Dec 2016 13:16:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cKqrS-00045D-3j for bug-gnu-emacs@gnu.org; Sat, 24 Dec 2016 13:16:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 24 Dec 2016 18:16: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.148260331115632 (code B ref 18133); Sat, 24 Dec 2016 18:16:02 +0000 Original-Received: (at 18133) by debbugs.gnu.org; 24 Dec 2016 18:15:11 +0000 Original-Received: from localhost ([127.0.0.1]:54004 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cKqqd-000443-Lh for submit@debbugs.gnu.org; Sat, 24 Dec 2016 13:15:11 -0500 Original-Received: from mout.gmx.net ([212.227.17.22]:60988) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cKqqb-00043q-VP for 18133@debbugs.gnu.org; Sat, 24 Dec 2016 13:15:10 -0500 Original-Received: from [192.168.1.100] ([212.95.7.50]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MH5Sw-1cOeCE0n5u-00Dn36; Sat, 24 Dec 2016 19:15:00 +0100 In-Reply-To: <83tw9txo31.fsf@gnu.org> X-Provags-ID: V03:K0:AqwCAuJaB3aBhZk+SMgGknbSXgovmp7z04fMCbRg4D+tIK+FWx4 HUtTojW0AJ40oXSodWJpG5kuESEqiBh/AaaB2THrsfzlv77M03TO2F1B0Qfau2WmfDX7fid M6UTwXcnPVK8uiuJlbxi8I7eYVEn/LGuEp5FZqkL2QWb2uoENjs3KZaDpn7z//TvQDPFCHh RpAHZxti3h/J3ztUYKIyw== X-UI-Out-Filterresults: notjunk:1;V01:K0:MdWURVV2VNA=:J7FPtt5y/qhpR12cxjNiKE yPppsxWzDEBDJ5hKo9yCKWeIya9f7m+knp2WY5upSFfAXLnhW5yhyegFAVu+j8EHgw7uTlQT8 Y46+IVtXKxSdxOxHfVvL2YORQ4V72y+w0ixRRP6Wofy206R6LEe4sYsXuo4XYaaSFUsX6RE2m nFJrCJQpzG8U3MCE/KfS0w4yHTXPvK2fIOee2+jCHLSOrKJrX/8oKWLhoBEYthu6i0HKE/r+G fJWpn2R8zxB7vkE4Gue1OZQJ9bJ0h0klGK7wQ1f5pfHSv6Vh1hVhkWQHXVV0Llkw2lAX124Rp Q1vtfYtLgG+VVdm4uAUljx3Jzk8wfnQ/7Hse/zdb1EtG1jdBbK6sawDEG+nTmyAhUkhQVNH4S vgY0jldsK9YAsEALbGXb7Z8XnqFvTOw8q/BflcOqXmf0ETe473fl29f/nIdYwrkL+zFSZjCdL SuoxDwb2rGcBjuTlCSrO4BNvTQOqOvH6mFhP427f1B98UFWVSNjbSMrxT0JoMyMBnDeenSuvB +yuAba1hgx8IfHtGXIypD23e8A/F4Aeoano8yrkqGQ1p2XmI6pkCfkGbWVALd6QfG6yICwDpi 3IQ6tL8fq18C9XA+B0C+OiDs7t6Kau8ltZU2koAzNvSKXzkw1nTirj/4mCSz/UAH5U8TKNYBO 8s+abNMNx6mNP67MNGATo5ahD1siwxgydRfZufs+ZG8w7q7ZXHbRxMgz2b+WLeeL4ei/3DBqY 1alpydEam9qpmxF2pJ6r7VfzMB3uHFtQv1cemskW1TmHOeTnRc1fDtNUIeU6MvZZ2azfdSPD 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:127416 Archived-At: >> It would be nice if the user only had to change one thing to enab= le hiding >> the async output buffer until there is output. If we only added t= he >> 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. > > Yes, I meant to add a value that would handle "*Async Shell Output*" > buffer like described above. The type specification of =E2=80=98display-buffer-alist=E2=80=99 goes as:= :type `(alist :key-type (choice :tag "Condition" regexp (function :tag "Matcher function")) :value-type ,display-buffer--action-custom-type) This associates regexps/matcher functions with actions. How, in such a specification, can I splice in a buffer name associated with a key _without_ assigning that pair to the default of =E2=80=98display-buffer-a= list=E2=80=99? Maybe I'm missing some detail of the customization interface. >> And how should =E2=80=98display-buffer=E2=80=99 know whether "there's= some material" in >> that buffer? > > That's up to Reuben, I thought he had this figured out already. Whatever he figures out, it will affect the decision whether to display the buffer initially. You can decide that via a matcher function in =E2=80=98display-buffer-alist=E2=80=99 (if the buffer name equals "..." a= nd the buffer is not empty display it, otherwise not) but then it would be easier to add a new action function like =E2=80=98display-buffer-if-not-empty=E2=80= =99. martin