From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eliza Velasquez Newsgroups: gmane.emacs.bugs Subject: bug#64394: [PATCH] Fix `async-shell-command-display-buffer' display Date: Sat, 01 Jul 2023 01:42:53 -0700 Message-ID: <87edls6n02.fsf@eliza.sh> References: <873528cuoe.fsf@eliza.sh> <833528rt62.fsf@gnu.org> <87h6qo6pbz.fsf@eliza.sh> <83v8f4qcdd.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30372"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rudalics@gmx.at, 64394@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jul 01 10:44:30 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qFWDU-0007fQ-1a for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 01 Jul 2023 10:44:29 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qFWD5-0005Of-P3; Sat, 01 Jul 2023 04:44:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qFWD4-0005OP-J9 for bug-gnu-emacs@gnu.org; Sat, 01 Jul 2023 04:44:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qFWD4-0003AC-As for bug-gnu-emacs@gnu.org; Sat, 01 Jul 2023 04:44:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qFWD4-0005ly-3k for bug-gnu-emacs@gnu.org; Sat, 01 Jul 2023 04:44:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eliza Velasquez Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 01 Jul 2023 08:44:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 64394 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 64394-submit@debbugs.gnu.org id=B64394.168820098822122 (code B ref 64394); Sat, 01 Jul 2023 08:44:02 +0000 Original-Received: (at 64394) by debbugs.gnu.org; 1 Jul 2023 08:43:08 +0000 Original-Received: from localhost ([127.0.0.1]:56543 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qFWCC-0005kk-EE for submit@debbugs.gnu.org; Sat, 01 Jul 2023 04:43:08 -0400 Original-Received: from out4-smtp.messagingengine.com ([66.111.4.28]:52563) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qFWCB-0005kK-0y for 64394@debbugs.gnu.org; Sat, 01 Jul 2023 04:43:07 -0400 Original-Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id DD2FA5C019E; Sat, 1 Jul 2023 04:43:01 -0400 (EDT) Original-Received: from imap48 ([10.202.2.98]) by compute5.internal (MEProxy); Sat, 01 Jul 2023 04:43:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eliza.sh; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1688200981; x=1688287381; bh=S4 vk7+aPl12LxTCiCKZsAu3/gxbDd99YydcX0Y3wbhM=; b=rlJDI47W9OKn+GQ3IK 2zNLUN6xtkeWNgstVCja53iBYXS4b6Eco3iGQsgIp2NtLRrcWfzr6cICMdlUoDpV wOmgbhiT8EOElw5v51Y9M0D9FnbJC6BPnOc2gKY2n/UhaPIBcxj/QzIAIN3T1iFm ao0wIyletJxW9Z5oCkK53mLu9O3CJz1Q88qhzhLqxw3CAb6Kq1b4g4nL/pkqYtRk 6yY4thpfu2nwO+KoTklNhBT51uZP/eJ8R27YvOb5v1LJJydkvufKhDTE+E3alVuI qkhPaFgE+7L5kNkXyE8eTKSnkjPhsTyiGSVzmlMxXMC4yLHjEsxCouhGqmcjq5j6 4Oyw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1688200981; x=1688287381; bh=S4vk7+aPl12Lx TCiCKZsAu3/gxbDd99YydcX0Y3wbhM=; b=U88Aax22k1vRPzraVeAR9EQDRPVdm sXk8XnEdLv24DPe0T9+X5TagIW4QUpMXs8XAgc4GtmKBeonH/gISrtbwKcvfx+zc Dhx+v+ZEcQ3VySKBUJ7yfIb6UgNqqOCK/8MxXta+/H8xCI0+m07ftX5vKsQtFIFS W15YA+BAyS9iT3B69ty9DopxrxAj6bpiRDaFJumBV5w6WqKm39UmDPiPh0qUb9b2 dTDYQnYKLzjrIjORmS25W4HnVUhVFJIzJsj5klT9TxLOoM1Rqn/PVNVXOFadK576 oodPlFXFILAzkzqBIuZrabT3zkeXqpNuHqC3yA9g7E2DiYBXQ6y4k8fwQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrtdekgddthecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefohffvvefujghffffkgggtsehttdertdertddtnecuhfhrohhmpefglhhiiigr ucggvghlrghsqhhuvgiiuceovghlihiirgesvghlihiirgdrshhhqeenucggtffrrghtth gvrhhnpeduleeffffghedvteekkeelgffhtdeitedvuefgtddttdfhueehtdeihfefvdet tdenucffohhmrghinhepghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepvghlihiirgesvghlihiirgdrshhh X-ME-Proxy: Feedback-ID: i87c446d8:Fastmail Original-Received: by mailuser.nyi.internal (Postfix, from userid 501) id 74DE031A0063; Sat, 1 Jul 2023 04:43:01 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface In-Reply-To: <83v8f4qcdd.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:264375 Archived-At: On Sat, Jul 01 2023 at 11:12 +03, Eli Zaretskii wrote: > But that's exactly what this variable is about, AFAIU: > > Whether to display the command buffer immediately. > If t, display the buffer immediately; if nil, wait until there > is output. > > Note the last part. > > So why do you think this behavior is a problem? On a philosophical level: It's surprising to me in that previous example that if `async-shell-command-display-buffer' is t, the buffer is /not/ displayed (according to `display-buffer-alist'), but if it's nil, it /is/ displayed, eventually (ignoring `display-buffer-alist'). On a practical level: The user may want to differentiate buffer display behavior based on the name of the shell command buffer or by some other predicate, including disabling showing that buffer, regardless of whether `async-shell-command-display-buffer' is set to t or nil. I have recently authored a package to make this easier [1] and ran into this problem. The example configuration in the README might shed some more light on the expected behavior. [1] https://github.com/elizagamedev/shell-command-x.el -- Eliza