From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#70949: display-buffer-choose-some-window Date: Tue, 21 May 2024 20:18:56 +0300 Organization: LINKOV.NET Message-ID: <86cypfm6s7.fsf@mail.linkov.net> References: <86jzjwqqmd.fsf@mail.linkov.net> <8d1947c7-a4d1-4920-8638-f8ae17acfe65@gmx.at> <86r0e32fnj.fsf@mail.linkov.net> <867cft0xt2.fsf@mail.linkov.net> <86ed9xvz3o.fsf@mail.linkov.net> <73251208-1e4c-4231-ae58-faf82363f241@gmx.at> <86jzjoo23l.fsf@mail.linkov.net> <9e29cbbc-65ee-4dd8-8a41-539946e19a7c@gmx.at> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1161"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu) Cc: 70949@debbugs.gnu.org To: martin rudalics Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue May 21 19:26:35 2024 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 1s9TFy-0000Bo-Ae for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 21 May 2024 19:26:34 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s9TFP-00027I-2G; Tue, 21 May 2024 13:25:59 -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 1s9TFO-00026o-1C for bug-gnu-emacs@gnu.org; Tue, 21 May 2024 13:25:58 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1s9TFN-0000dY-P1 for bug-gnu-emacs@gnu.org; Tue, 21 May 2024 13:25:57 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1s9TFS-0001F7-Le for bug-gnu-emacs@gnu.org; Tue, 21 May 2024 13:26:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 21 May 2024 17:26:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 70949 X-GNU-PR-Package: emacs Original-Received: via spool by 70949-submit@debbugs.gnu.org id=B70949.17163123424742 (code B ref 70949); Tue, 21 May 2024 17:26:02 +0000 Original-Received: (at 70949) by debbugs.gnu.org; 21 May 2024 17:25:42 +0000 Original-Received: from localhost ([127.0.0.1]:50241 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s9TF8-0001EQ-8g for submit@debbugs.gnu.org; Tue, 21 May 2024 13:25:42 -0400 Original-Received: from relay2-d.mail.gandi.net ([217.70.183.194]:33517) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s9TF3-0001EK-Pg for 70949@debbugs.gnu.org; Tue, 21 May 2024 13:25:41 -0400 Original-Received: by mail.gandi.net (Postfix) with ESMTPSA id 8876240003; Tue, 21 May 2024 17:25:05 +0000 (UTC) In-Reply-To: <9e29cbbc-65ee-4dd8-8a41-539946e19a7c@gmx.at> (martin rudalics's message of "Tue, 21 May 2024 10:21:14 +0200") X-GND-Sasl: juri@linkov.net 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:285545 Archived-At: > +The above describes the behavior when @code{some-window} @var{alist} > +entry is @code{lru} or @code{nil} which is the default. But when, > +for example, @code{display-buffer-base-action} is customized to > +@w{@code{(nil . ((some-window . mru)))}}, then the value @code{mru} > +means that this function will prefer the most recently used window > +that is useful to display several buffers in the same window > +in a layout with more than two windows. > > This is ambiguous - we should emphasize that these buffers are not > displayed at the same time. I'd write something like the following: > > The default behavior might become irritating when 'display-buffer' is > used to display a number of related buffers in a row. > > Consider a configuration of two or more windows where a user wants to > consult, in a non-selected window, one after the other, the results of a > query spread among several buffers. With the 'lru' strategy, Emacs > might continuously choose another window because the least recently used > window changes with every call of 'display-buffer-use-some-window'. > With the 'mru' strategy, the window chosen would always remain the same, > resulting in a less confusing user experience. > > If I got it right ... Not quite right. It's not about a less confusing user experience. Here is what the OP wrote for this request: I'd rather have file results remain in just one window so that I can use other buffers while still viewing search results. Probably here would be better to say not "other buffers", but "other windows".