From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#45688: 28.0.50; New action for display-buffer? Date: Sun, 10 Jan 2021 17:05:36 +0100 Message-ID: References: <87im8a1dff.fsf@gnus.org> <83y2h6133r.fsf@gnu.org> <8735ze0yp7.fsf@gnus.org> <83o8i20w1f.fsf@gnu.org> <87lfd5yny9.fsf@gnus.org> <87o8i03gem.fsf@gnus.org> <528b7d6b-403a-ffef-b0a0-4a0b6d92bec8@gmx.at> <87turpvxv0.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17846"; 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 Sun Jan 10 17:07:51 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 1kydFu-0004Yv-Ue for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 10 Jan 2021 17:07:50 +0100 Original-Received: from localhost ([::1]:42296 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kydFu-0000Gy-0y for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 10 Jan 2021 11:07:50 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53586) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kydEA-0007Jx-7D for bug-gnu-emacs@gnu.org; Sun, 10 Jan 2021 11:06:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:43204) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kydE9-0001Sl-Ua for bug-gnu-emacs@gnu.org; Sun, 10 Jan 2021 11:06:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kydE9-0004LU-Oq for bug-gnu-emacs@gnu.org; Sun, 10 Jan 2021 11:06:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 10 Jan 2021 16:06:01 +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.161029474716674 (code B ref 45688); Sun, 10 Jan 2021 16:06:01 +0000 Original-Received: (at 45688) by debbugs.gnu.org; 10 Jan 2021 16:05:47 +0000 Original-Received: from localhost ([127.0.0.1]:54750 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kydDu-0004Kr-Lo for submit@debbugs.gnu.org; Sun, 10 Jan 2021 11:05:46 -0500 Original-Received: from mout.gmx.net ([212.227.15.18]:47047) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kydDs-0004Ka-R1 for 45688@debbugs.gnu.org; Sun, 10 Jan 2021 11:05:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1610294739; bh=gVsGsvxj09TBiKISHbGrtDMJs4ftWmyAgObrzu9UMqo=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=lTInoi4fMbJYO26SXtGGVqXWkRHJ7XfoKhWacEpPaGgXMPZIelGj2jXSIjtuppakR n9B5H0Dq2cFBMajx595D/n2T4Ch2XIHUD9BTrQ5qmYypDwc1X6icHa0qYqmah51hsy 3phhLgWL+JNgaZx92svwxotHC6ZMmAOzcOnj05MQ= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.100] ([212.95.5.93]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MFbW0-1kjlvA2Wv0-00H3sx; Sun, 10 Jan 2021 17:05:38 +0100 In-Reply-To: <87turpvxv0.fsf@gnus.org> Content-Language: en-US X-Provags-ID: V03:K1:Q9O3IzDTcLkq7Slutmst83VePjeEJgx9tC/Dve2036YzIv5Gcdg 4deXrjxoOHXcoFk/ZsVF5/UEXX8kJzALzKrK8ew4a3sLYKLebr3Qe2jC1aL070G6nMgErK0 kxIHk1KN2W/dnaks9SFYiptgQD1w0afMDvtotXIIIDVOP9E8519KXwhNSep4BL7tR03WRnx GOmM1I8TGvOvD4hQc8DmA== X-UI-Out-Filterresults: notjunk:1;V03:K0:PLZWyJ3xzOk=:qsXbeYOl/L/HKUPiC7C5gm wa164RMe27OJYGmL8CTaGV0QLFW3ks3utrsHiooldQNXLbTkprUid8zQYfEOCSaG4hJuLz1oX pyChKiSR8SGnOkKh/KxyRG6xNndxGP78hCnFmtN1HkDqp6Y3E4suyEO7m/pThNYm3/QEB6L0V zqukCeuW5dGYA5yIdWOhaLP2JLkCkSA9wDYFi8nzfIF7s9gDqw/WPnZ6zcdRowAgFF52zVQaz F9UzQuVlg/THQcyDfmnCujy7+mndsnp0g+Zpzhez1Z8wnHYaRjNLrWE4/VRpVX/i1M2hnYLvh D+TNDPc5S/a8oyrUbR4/Sd41YLVAVTaf0cZiswPIEC6MqRkUwnWorQPpUbI59IJkx7P3BVpAM jP7donrXx+Fqjfqiy8qXMkFKoRIU2RPx3OmPHhVUaYidWsvJY11VKZLO3HCkVucxuZ7ez0QnY 9grstJy1MWlJA6m3I43Ra8AmUsKsSVsUkK4ct0GbcYgFIKLKMWotop187DPo4Uwbqc42ZOQFo 1dT4b1hc73VPC5RmH8K7wXAgLes8DEeTqNekBILyq5KdQeb4+S9hvK2PQkiI+dVDpy6o2ezrC V1qqJ3+nOnNF/eGvEYImlIMbLNovrXznNEMcS7oEGqcomikzM0TsSEkCiaIJjASlQ6JOtDjJ1 y2Vpud+HXyPTB5/bnuwbz4N39euS4sBEhVmX84ktMZqmOSGqZh/LlUkMSyVOCJRwJE8sHc3kC 0MZg06QenRdyVq2DEDEypJBr7fvWCO+JljEuv1eO9Ma197nqdSdFPaoipEwPnHLP9FgKsN2u 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:197638 Archived-At: >> This >> >> + (when-let ((window (display-buffer-use-some-window >> + buffer (cons (cons 'inhibit-same-window t) alist)))) >> + (window-bump-use-time window))) >> >> alone will bump the use time for a _reused_ window only. A freshly >> popped up window will continue to be the first candidate for reuse and >> only then enter the cycle of windows to reuse. > > How do we bump the use to for a new window, then? By bumping the time stamp of _any_ window 'display-buffer' uses for displaying a buffer (just like XEmacs does). >> XEmacs treats _all_ windows it creates or uses equal in this regard >> including those on other frames. > > Oh, other frames, too... I think we'll leave that as an exercise for > the reader. Then when you switch from one frame to another, any problems you've found on the previous frame will immediately reemerge on the new frame. >>> The only oddity is that it'll resize windows to their previous sizes -- >>> is there any way to inhibit that? >> >> How comes that window gets ever resized in the first place? > > I have no idea, but it's totally repeatable -- the window that's > switched to becomes the largest window, and it's rather distracting. Please put some silly function on 'window-size-change-functions' and make it produce a backtrace. martin