From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#45688: 28.0.50; New action for display-buffer? Date: Wed, 06 Jan 2021 20:17:48 +0200 Message-ID: <83o8i20w1f.fsf@gnu.org> References: <87im8a1dff.fsf@gnus.org> <83y2h6133r.fsf@gnu.org> <8735ze0yp7.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11324"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 45688@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jan 06 19:18:28 2021 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 1kxDO7-0002qX-OP for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 06 Jan 2021 19:18:27 +0100 Original-Received: from localhost ([::1]:41398 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kxDO6-0007hv-OK for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 06 Jan 2021 13:18:26 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51540) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kxDNi-0007gM-HX for bug-gnu-emacs@gnu.org; Wed, 06 Jan 2021 13:18:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:33950) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kxDNi-0002RG-9o for bug-gnu-emacs@gnu.org; Wed, 06 Jan 2021 13:18:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kxDNi-0007gP-42 for bug-gnu-emacs@gnu.org; Wed, 06 Jan 2021 13:18:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 06 Jan 2021 18:18:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 45688 X-GNU-PR-Package: emacs Original-Received: via spool by 45688-submit@debbugs.gnu.org id=B45688.160995707929524 (code B ref 45688); Wed, 06 Jan 2021 18:18:02 +0000 Original-Received: (at 45688) by debbugs.gnu.org; 6 Jan 2021 18:17:59 +0000 Original-Received: from localhost ([127.0.0.1]:45496 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kxDNf-0007g7-Gq for submit@debbugs.gnu.org; Wed, 06 Jan 2021 13:17:59 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58376) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kxDNe-0007fv-3V for 45688@debbugs.gnu.org; Wed, 06 Jan 2021 13:17:58 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:38136) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kxDNY-0002NV-SM; Wed, 06 Jan 2021 13:17:52 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2945 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kxDNX-0004ZH-Vr; Wed, 06 Jan 2021 13:17:52 -0500 In-Reply-To: <8735ze0yp7.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 06 Jan 2021 18:20:20 +0100) 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" Xref: news.gmane.io gmane.emacs.bugs:197441 Archived-At: > From: Lars Ingebrigtsen > Cc: 45688@debbugs.gnu.org > Date: Wed, 06 Jan 2021 18:20:20 +0100 > > Eli Zaretskii writes: > > > I'm not sure I understand what kind of use case would find the above > > convenient. display-buffer is supposed to be for temporary display of > > some buffer that you soon enough want to go away, so why does it > > matter which buffer it replaces? > > It's a user command (on `C-x 4 C-o'), and apparently some people use it > a lot? I use it myself, when some buffer pops up in a window I use for another buffer, and fails to pop down (example: *Shell Command Output*). But then why would I want the buffer be displayed in a random window? > I've never used it myself, but I see the charm -- if you want > to look at a different buffer while working in the current buffer, it > seems quite convenient. Sure, but once again: why do that in some random window, as opposed to a fixed one? I'm not asking about the utility of display-buffer, I'm asking about this particular aspect: the fact that it doesn't pop up in a fixed window. I guess I'm missing something here, if this feature is deemed so important that it caused jwz to post a complete blog about that.