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#33532: 26.1; set-window-configuration does not restore display start Date: Thu, 06 Dec 2018 10:09:54 +0100 Message-ID: <5C08E762.7060303@gmx.at> References: <87efb62mt2.fsf@metalevel.at> <83o9a9g0ui.fsf@gnu.org> <877egxyvje.fsf@metalevel.at> <5BFFA3FB.4060603@gmx.at> <8736rj4uxg.fsf@metalevel.at> <5C0039D0.2090309@gmx.at> <877eguqz7k.fsf@metalevel.at> <5C0177B2.4030803@gmx.at> <87va4cdfll.fsf@mail.linkov.net> <5C03991F.8030204@gmx.at> <87ftvftoaq.fsf@mail.linkov.net> <5C04DF22.3030100@gmx.at> <87a7lmqkry.fsf@mail.linkov.net> <5C063BCA.3090301@gmx.at> <87k1kp9e4y.fsf@mail.linkov.net> <5C07978B.4050206@gmx.at> <877egn1nua.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 1544087503 4330 195.159.176.226 (6 Dec 2018 09:11:43 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 6 Dec 2018 09:11:43 +0000 (UTC) Cc: 33532@debbugs.gnu.org, Markus Triska To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Dec 06 10:11:39 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 1gUph4-00010X-Uw for geb-bug-gnu-emacs@m.gmane.org; Thu, 06 Dec 2018 10:11:39 +0100 Original-Received: from localhost ([::1]:39703 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gUpjB-0002Y7-AW for geb-bug-gnu-emacs@m.gmane.org; Thu, 06 Dec 2018 04:13:49 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54359) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gUpgX-00078M-Iz for bug-gnu-emacs@gnu.org; Thu, 06 Dec 2018 04:11:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gUpgU-0004Fq-D4 for bug-gnu-emacs@gnu.org; Thu, 06 Dec 2018 04:11:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:58932) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gUpgU-0004FN-5u for bug-gnu-emacs@gnu.org; Thu, 06 Dec 2018 04:11:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gUpgU-0001nq-04 for bug-gnu-emacs@gnu.org; Thu, 06 Dec 2018 04:11:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 06 Dec 2018 09:11:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 33532 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 33532-submit@debbugs.gnu.org id=B33532.15440874176864 (code B ref 33532); Thu, 06 Dec 2018 09:11:01 +0000 Original-Received: (at 33532) by debbugs.gnu.org; 6 Dec 2018 09:10:17 +0000 Original-Received: from localhost ([127.0.0.1]:34957 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gUpfk-0001me-Nq for submit@debbugs.gnu.org; Thu, 06 Dec 2018 04:10:16 -0500 Original-Received: from mout.gmx.net ([212.227.15.19]:48687) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gUpfg-0001mL-J4 for 33532@debbugs.gnu.org; Thu, 06 Dec 2018 04:10:13 -0500 Original-Received: from [192.168.1.101] ([212.95.5.6]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M1Ee8-1hJEQd0wae-00tFwp; Thu, 06 Dec 2018 10:10:03 +0100 In-Reply-To: <877egn1nua.fsf@mail.linkov.net> X-Provags-ID: V03:K1:KxqP9QrNyBGfs/hIOZayZtY8edjtahIh35v2hPY++UyOHLjn2Ox 17BRg6PUS02Fq6CmwzUAni5mltZf4LQ9b3w2pi3y5zFryOHHNQb2egks9mSYYLaPopAvHPX 5AfysLvVNGGfrcRLU82fUSmr6us7iqz9hLyIKooxvBD0McuBhkK5Iueugo2qW5hydTziLNm tO84qxxznDZ+OvqTrgtnw== X-UI-Out-Filterresults: notjunk:1;V03:K0:Y5+C1rrZEgk=:xqSELweYM81KCpC/PtKkUq Il47kQHOpcgprIumldCf6XW1kM1Uzh4yp3B0RDSIpF2FmR1cAO5DqDWnWDFERdthkP/q0z23C QCSoiS382BcO0AndwgPXtDb2itDKPf8U46alRgM/gyQcZoKDpf9jsjX/HPrvXC1wX9Tg3Ebba G8SI7AKpUfv1sz3gmRR8Y97/Fx9UuH1dMEfJ7ON1yg/S9rFlMAHHHuIpUksd9iRZYq7C/pkah fE2/cLyzCABnmxEKzT8WyQDBUw0x+jtUPYBeWc5xtrfmxCzsRbOpk7iP04yjcWHN51h/6t1cy gaBcrq41MaTsAxukSFFAbsn/2NGmUwTmwVD+TfvwwKHrAGgEoiwmnyTvvAhtxVOgKiZialzr4 U1HuDqgiojx/lHVMIUv/rceUby/vUZLdZ2jZsHSoBY2iO8kL/2bwkz/qagPgPGmDNI9KZvN07 kFK2zCpa/xtrKZc1PB+mvCn4fNSiyvWduAB6FF7FiFNkQjGEaQMgPON2BojeYdOSyE1ZkYZDO cXaOlzEVEIf3tbyXG72RW0tumpw82YQ5RzJIRNW8B52PyHvWsM3KRKxhqqrd4laPmoHEJzi0d VMTFfYzCQMlHdl8/BmrCI1XpVyiMziCHVRrfsB99jsOh9UyxeskzZXKrkhcJeHBrvBeG0tWMs Rr6kRn1tJciRjvu81BOcq6Z2npo5gNOlkMnmQm0zhtWgNOKXvrNzD6i33X4Ugiviy2f3LSyp+ 3vBUoaUDVsrrlYtsP6cmLjF6RMltoN2SgyxODFMyl3w7uxy5XBDA0IlS9lvWDD2cYbvQ2mb7 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:153143 Archived-At: > Then maybe instead of immediately modifying values in windows (like > e.g. comint-postoutput-scroll-to-bottom uses get-buffer-window-list > and comint-adjust-window-point) and instead of trying to do the same > in window configurations/states, better would be to modify these values > when windows are restored from window configurations/states/prev-next-buffers? That was my idea when I proposed to go to the buffer's point when restoring a configuration/state and the buffer had been reverted since the configuration was saved. Note that a configuration already has to display some live buffer when the one it stored got killed since it was saved. Still, it might not be what users want, especially if they use configurations to show the same buffer in multiple windows. Note in this context that the collector does not scan window configurations specially (or at least I cannot see where it does that or whether any pointers in a configuration are weak). So if you save many configurations (or states) and kill buffers often, the dead buffer objects and the markers these configurations save - including those from the windows' previous and next buffers - will steadily pile up. If someone knows better, please correct me. martin