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: Wed, 05 Dec 2018 10:16:59 +0100 Message-ID: <5C07978B.4050206@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> 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 1544001388 17856 195.159.176.226 (5 Dec 2018 09:16:28 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 5 Dec 2018 09:16:28 +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 Wed Dec 05 10:16:24 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 1gUTI7-0004WJ-TT for geb-bug-gnu-emacs@m.gmane.org; Wed, 05 Dec 2018 10:16:24 +0100 Original-Received: from localhost ([::1]:33010 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gUTKE-0005Vp-Eb for geb-bug-gnu-emacs@m.gmane.org; Wed, 05 Dec 2018 04:18:34 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41481) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gUTJt-0005N6-16 for bug-gnu-emacs@gnu.org; Wed, 05 Dec 2018 04:18:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gUTJk-0002UA-Bf for bug-gnu-emacs@gnu.org; Wed, 05 Dec 2018 04:18:12 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:57089) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gUTJi-0002Sr-T8 for bug-gnu-emacs@gnu.org; Wed, 05 Dec 2018 04:18:04 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gUTJi-0007Ny-Ny for bug-gnu-emacs@gnu.org; Wed, 05 Dec 2018 04:18: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: Wed, 05 Dec 2018 09:18:02 +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.154400144028325 (code B ref 33532); Wed, 05 Dec 2018 09:18:02 +0000 Original-Received: (at 33532) by debbugs.gnu.org; 5 Dec 2018 09:17:20 +0000 Original-Received: from localhost ([127.0.0.1]:33110 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gUTJ2-0007Mn-HQ for submit@debbugs.gnu.org; Wed, 05 Dec 2018 04:17:20 -0500 Original-Received: from mout.gmx.net ([212.227.15.19]:39129) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gUTIy-0007MW-8I for 33532@debbugs.gnu.org; Wed, 05 Dec 2018 04:17:16 -0500 Original-Received: from [192.168.1.101] ([212.95.5.150]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LvV1X-1hTClt2Qy3-010bOf; Wed, 05 Dec 2018 10:17:06 +0100 In-Reply-To: <87k1kp9e4y.fsf@mail.linkov.net> X-Provags-ID: V03:K1:S7Y8GlswFSNacwvOzk8EqbAF4pYDnKM9hRNGtD3UcdwlFB3qSUQ Kp6jEWhpZYkv+V6Vxvi3fmT7THS3wrHTwzG0FUAhj+kNRXf1jCZDQ3mlVPsx0rJTY63kzeN 0AJGyKUkJoZx4l+PkbI10NCkltHIlIv3+pH9paVxN/o3N/JzUAlzo1K9gcadyph7vHp1l5w /3Ic1czlRPeEjmJJ1YPNw== X-UI-Out-Filterresults: notjunk:1;V03:K0:SHQDzTAD/Bw=:JzRGgFoq21UrP+nnHQ17U8 5Z4eVXSAKjWlXf9q8ySfgIVSppLcVkpGD+F3enS6wTE6/cllPYwvaAgma8DeNxmi3MhIBR7hJ S2JtUn/3bo7zW+XRCfB3ZzVP82hTB3sxyTLZ+XVRh+cUJjGQ1PkKfkGdnzDUoZLBoRzHIiPPL 20rTqukBcFaBjQAMMGVIdJ9hE6YMVRxeSc1vrJk4xSq8iuacqRsajkPyXMW+rb6Qomwg3RyJW kUYOY663SneHjD/6wl5gQV+Rrgp2t/ljqmEY5JJerbBF2OgMWrtOEozdqBwsyujIdHSLQArcx wm8oe7/wJOJ/KdKaAuFXCwBwmPaDyQhzn3TpFqZPa5SXRpB5tRRDXrkLqdEIM7LW0qcYmXgz/ L9Kb1KpSgEY75mxiAd2T1rM4MBIEsGA6lv1WbvUDUf6uUpSVdt/FjngxQG+Pp7rw059CHQFVh AsyT+9wkQcDX40cgzUrbDSTI1z6i9+spsoaAeYmtbIf2C7e6E09p7W1J8eje5FUd8vf8YwgDB 34tq2zYoQlfyuC+yr9wYYHbYNbCuDJFW0tbdDOzb7ldhD0FY/Z6uy3XOvhdzdMXRK9oClmtgf w1Q4t6Z27EtqM8CzP/DERzarv0e6jLHLdHs/IA2iJ1tkUQycvrJZWLlYOjrSvDr/Gza8/LxUI dyUCxTlZm6M1r1mYHov5FpvwedK9zzF6J+pfqmUaCjm6BKcJ5HYKtdVY5ktmvAEoeJcia0SSx wfnyyB6BYLEDa3tQbmHcIvlCoxtVz5ODnnOYWJ2eSyBOwdkZP5Q4gxNC528U1LJ14j0Gc0yS 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:153100 Archived-At: > Again, no support for window configurations and non-writable window > states. But maybe it's possible to access all buffer's windows, > even windows in window configurations/states, and changes their > window points, including previous buffers' points in window > configurations/states. How would we handle window configurations? We could add a new variable say 'window-configuration-list' and make sure that configurations accessible from that variable are scanned by revert buffer functions. Applications and users would be responsible for removing a configuration from that list when it's no more needed. But we also need accessor/setter functions for Lisp slots like the windows stored in the configuration and for any such window its list of previous and next buffers (where "any such window" could be a deleted one). Doable but certainly non-trivial. Window states would have to be handled in a similar way. But there the task would be simpler: Add a variable, say 'window-states-list' and if a state is on that list, reverting a buffer could scan it right away. Doable but still requires some work. > BTW, I understand why reverting a dired buffer moves its point-marker to > the beginning of the buffer in the selected window window restored from > a window configuration. But I don't understand why point-marker is > moved to the end of the dired buffer in non-selected window restored > from a window configuration. I have no idea either. martin