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#32825: 27.0.50; Deterministic window management Date: Fri, 16 Nov 2018 09:53:27 +0100 Message-ID: <5BEE8587.9090702@gmx.at> References: <874leeaiah.fsf@mail.linkov.net> <5BE154F5.4050902@gmx.at> <87r2fxsvl5.fsf@mail.linkov.net> <5BE2AF02.40909@gmx.at> <87sh0cva5h.fsf@mail.linkov.net> <5BE3F981.8000002@gmx.at> <8736sbmdtv.fsf@mail.linkov.net> <5BE54FBE.306@gmx.at> <874lcqmu6u.fsf@web.de> <5BE582D4.8010201@gmx.at> <874lcok62x.fsf@mail.linkov.net> <5BE7EE09.3020003@gmx.at> <87pnvbpejc.fsf@mail.linkov.net> <5BE93DB5.8070804@gmx.at> <87wophvpag.fsf@mail.linkov.net> <87efbprc1h.fsf@mail.linkov.net> <5BEA9577.1080204@gmx.at> <87sh047dzh.fsf@mail.linkov.net> <5BEBDDE6.1030701@gmx.at> <87sh03jjxm.fsf@mail.linkov.net> <5BED388E.7030506@gmx.at> <875zwyuicg.fsf@mail.linkov.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1542358337 11524 195.159.176.226 (16 Nov 2018 08:52:17 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 16 Nov 2018 08:52:17 +0000 (UTC) Cc: Michael Heerdegen , 32825@debbugs.gnu.org To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Nov 16 09:52:12 2018 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 1gNZrI-0002uM-BS for geb-bug-gnu-emacs@m.gmane.org; Fri, 16 Nov 2018 09:52:12 +0100 Original-Received: from localhost ([::1]:43021 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gNZtO-0005Uf-V3 for geb-bug-gnu-emacs@m.gmane.org; Fri, 16 Nov 2018 03:54:23 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49460) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gNZt9-0005Tq-4p for bug-gnu-emacs@gnu.org; Fri, 16 Nov 2018 03:54:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gNZt6-0003RQ-BG for bug-gnu-emacs@gnu.org; Fri, 16 Nov 2018 03:54:07 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:50455) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gNZt6-0003RC-52 for bug-gnu-emacs@gnu.org; Fri, 16 Nov 2018 03:54:04 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gNZt5-0008KZ-VV for bug-gnu-emacs@gnu.org; Fri, 16 Nov 2018 03:54:04 -0500 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 16 Nov 2018 08:54:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32825 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 32825-submit@debbugs.gnu.org id=B32825.154235842731993 (code B ref 32825); Fri, 16 Nov 2018 08:54:02 +0000 Original-Received: (at 32825) by debbugs.gnu.org; 16 Nov 2018 08:53:47 +0000 Original-Received: from localhost ([127.0.0.1]:54713 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gNZsp-0008Jw-Ce for submit@debbugs.gnu.org; Fri, 16 Nov 2018 03:53:47 -0500 Original-Received: from mout.gmx.net ([212.227.15.19]:42687) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gNZsn-0008Jh-GO for 32825@debbugs.gnu.org; Fri, 16 Nov 2018 03:53:45 -0500 Original-Received: from [192.168.1.101] ([212.95.5.219]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MWTfu-1fyxcw3wdu-00XcDT; Fri, 16 Nov 2018 09:53:37 +0100 In-Reply-To: <875zwyuicg.fsf@mail.linkov.net> X-Provags-ID: V03:K1:NxIKefos4uuHlVfhjb8g6s22uAq6jkhLQR8kfhAiy1pzqOcNFfs d7NN8t1vL7upDF6mPWQutDUf8b5itEOjEG6JUTHYrARO3V318YB/WgfY2QXfsOPolDgjSsC 4KFDJNSO4c7s8kPvlF64kWRlHzDzzGFJp8OoY9aLrP3TUTtMyWfoa523P++oZEU1L0a2sqI cFylA4hL6Rn3d5xaTVlOg== X-UI-Out-Filterresults: notjunk:1;V01:K0:qWxdC4vaXho=:5MMCdtkqEjs7ASx+XzCEvm M+qTHG9+KfPlntUd6Cq9NQOR9og/P0ACj2b7YMe+p7G7duCa6cS2ZnXBsIBQ9J03zMhFeTue2 c2q+uY4d2+pqD0X1p4h/AygvNscju9pQg29MYT/FQVftawXvia4SIgdWNEf2eq8tFzW35J+qI rd5JNTJRGuUmR/aIYDuDErxRRv7bGQki4H9wXNv6tBWOfosham9T1MdDEi0wUrtrdVef4hGk9 YchtPdimLWj4Cc+L+iXmpORvBbaf9YEugUHWjxTIgCh4RESvvG524kC3I1NiS9K3BGl/2+Q6W YKnJ3mWf3dS2CfvLCKpJOsLuzbDpOusp+8qy5It2WIV+tweI5kM9BNJfoCpJ/0fmZJWvf0hi2 /v1+lyt16a4PfJc5rniexd7QO3SWSoFM6bIIOGDFOgouHODKZhrGey0ZltnV3Y+PZutHNFwDo 1nXeDsO34Np9tZh/yqLe9oI+oMzxfEiNxFrKa9TuMMN8rhiuq673y3h9i1bI0xVIPSHKzXL9f 7g8ai99WZdoqbwv/x9qqju/1jzU1v6vRHcdAOGcPRZl8HSV6OlsZMmoH9/3U7NOlzXLjwbOgk XMJhbr8cPtL2XEhGpltSjbSJ5jM3AZIRgDmQuR57orYYaHPFp3Iki4wgIpmL690pD/rmRZz6u fH2M1vB36RxHQnfNuqpqVPeOCs8k0LVo4JTfPOjHRIL8TtPFujjxyYVBsijv4v2ijJeKH2uZ9 2Z+Fwzoo/65PnqzyjWXQUFjL2GxuzMFNZDZpDTgENC2SLybVp4vTVqBcHGCrqubnE+x3jLjA 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:152445 Archived-At: > The need to skip. If the original window was too small > to split and display the buffer in a new window below, then > if some existing window is reused to display the temporary buffer, > it's understandable for the user why that temporary buffer is shown > in the window-local tab-bar. > > At least, then the user will see in which window the same buffer > will be reappear again - in the same window that shows this buffer > in its window-local tab-bar. The latter is a visual feedback. But if I blindly use C-x left, I'd still be surprised. > The second time when the buffer is displayed again in a previous window > is deterministic. But the first time it is non-deterministic - it's > displayed in a random window. At least, the user can't predict the > window where it will be displayed - thus the surprise factor. > With get-mru-window instead get-lru-window the place is more > deterministic because the user usually remembers which window is mru. We can add an action alist entry to get the mru (or better mru-not-selected) behavior. A small deal. >> When people work with two windows simultaneously, the mru one is >> usually the "other" window they work with, maybe showing the same >> buffer at a different location. I think it would be a bad idea to >> punish such users by reusing the other window for showing some >> temporary buffer instead. > > Right. Neither lru nor mru should be used to steal existing windows > from users to show temporary buffers. Only new windows should be > created below or on the bottom. > > But my complaint about get-lru-window is that it prevents me from > using more than two windows. ... the way you want. > When I create three windows or more, > then get-lru-window always selects a wrong window. Is it possible > to change get-lru-window to get-mru-window to allow using three windows > and more on the same frame? Earlier we discussed whether "creating a window" should also mean "using that window". This could be yet another action alist entry - bump the use time of the window used for displaying a buffer even when it's not selected. I suggest you try adding this and the one providing mru behavior I mentioned above, experiment with them and install them if they give good results. martin