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#32790: 27.0.50; point jumps unexpectedly after delete-window Date: Sun, 28 Oct 2018 09:59:57 +0100 Message-ID: <5BD57A8D.8080408@gmx.at> References: <87efdnsp2k.fsf@mail.linkov.net> <87pnx1h1op.fsf@mail.linkov.net> <5BAB489E.5090002@gmx.at> <87h8ibvrs2.fsf@mail.linkov.net> <5BAD2507.6040605@gmx.at> <87a7nedidg.fsf@mail.linkov.net> <5BC5A558.9010401@gmx.at> <87zhvd7mg9.fsf@mail.linkov.net> <5BC6E52F.2070209@gmx.at> <87woqgw9a7.fsf@mail.linkov.net> <5BC83EC9.1090808@gmx.at> <877eiena58.fsf@mail.linkov.net> <5BC98A26.1030901@gmx.at> <87woqcnwas.fsf@mail.linkov.net> <5BCC3757.9020204@gmx.at> <87bm7njk2f.fsf@mail.linkov.net> <5BCD934D.4070906@gmx.at> <878t2owo8i.fsf@mail.linkov.net> <5BD03F4D.1000900@gmx.at> <87in1phhx2.fsf@mail.linkov.net> <5BD2C52E.2060607@gmx.at> <87ftwrgwp2.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 1540717153 4620 195.159.176.226 (28 Oct 2018 08:59:13 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 28 Oct 2018 08:59:13 +0000 (UTC) Cc: 32790@debbugs.gnu.org To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Oct 28 09:59:09 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 1gGguZ-00014q-Lt for geb-bug-gnu-emacs@m.gmane.org; Sun, 28 Oct 2018 09:59:07 +0100 Original-Received: from localhost ([::1]:39337 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gGgwg-00047M-64 for geb-bug-gnu-emacs@m.gmane.org; Sun, 28 Oct 2018 05:01:18 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45074) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gGgwV-00046f-GE for bug-gnu-emacs@gnu.org; Sun, 28 Oct 2018 05:01:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gGgwQ-0006wY-F0 for bug-gnu-emacs@gnu.org; Sun, 28 Oct 2018 05:01:07 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:42395) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gGgwQ-0006wO-Al for bug-gnu-emacs@gnu.org; Sun, 28 Oct 2018 05:01:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gGgwQ-0008Ns-91 for bug-gnu-emacs@gnu.org; Sun, 28 Oct 2018 05:01:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 28 Oct 2018 09:01:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32790 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 32790-submit@debbugs.gnu.org id=B32790.154071720832151 (code B ref 32790); Sun, 28 Oct 2018 09:01:02 +0000 Original-Received: (at 32790) by debbugs.gnu.org; 28 Oct 2018 09:00:08 +0000 Original-Received: from localhost ([127.0.0.1]:46650 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gGgvY-0008MV-K7 for submit@debbugs.gnu.org; Sun, 28 Oct 2018 05:00:08 -0400 Original-Received: from mout.gmx.net ([212.227.15.18]:55381) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gGgvX-0008Kx-48 for 32790@debbugs.gnu.org; Sun, 28 Oct 2018 05:00:07 -0400 Original-Received: from [192.168.1.101] ([212.95.5.102]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MAxyW-1gOMR90nxM-009v4O; Sun, 28 Oct 2018 09:59:59 +0100 Original-Received: from [192.168.1.101] ([212.95.5.102]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MAxyW-1gOMR90nxM-009v4O; Sun, 28 Oct 2018 09:59:59 +0100 In-Reply-To: <87ftwrgwp2.fsf@mail.linkov.net> X-Provags-ID: V03:K1:qtH62OEHQ0yDUA03bRdGyh6ivYzPxQkLVs/D7ur1C+E6t8be6zI LZB1MFtPKpwGA9f/fouSQhFToLd52ZOVHEGK4UPIxsThHemL9CAkcggMMQFG1Ce+GQ8o2xi 4rEWTru8/FQDtwAnCgaDdc1NEaCJFYBavGzDg1xJJyRrjvxtcvUi0CZgcsvNCRvtlGbN1ym SVq8dNKjnf4LhyIQJLqsQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:iDk6MiXEM1o=:HwT3UTRMMN/VS2Dg8w2Zh1 khPGe/l6Bfrz44kp18wwJqvDNSEvUb7F1/BWyhsaqx1f3y6WXMnebxbfxvMaLuESv4VikU4Ef fev3NvqyHt6VM7HJkw5c+h59eA+81Q4RAvhLsyB8fm2S8JpCkwZhhMWzjIMe960x8xmnCTQSw haxOcQVc7fKEXFbY3hcLkKeithJcMsYypzoRUmJTx3GERF/ehpZCAYBtgEyM/6TBl8j128Br8 v9hUqSvT66knhyyoCeaIUK1MiCs2hAV3e5/UNxOau0LhwqeCo/DWAi2lzMszkaxTwUCJ1wBSR CJcqzUI0rSF3GvAW7ZPr2g1s/dIRNezMMsLmelmZ7LEPF5CBIGOB/ZzxWfNC1/6i2/3aybzjO nHEpanA13uDyLbMp19IN/CJdMMfMqc08ez1+vQAZisZctlpB0qzwT26ES+nlyvmeFAmvLN/Ko VUGugcbdoBJ7BbFUQwDOOxCZixB9p8BQ3oPZVxpDMRZe6D/UWgX5HJeCfBmOquPq9KWrGU+x6 JN7qQEzrHqPpMwQAOOwLw3F+l5DqRfu7/MQnh+SqwuN9NgvI/kjjU1rDG0GbKJyqiA+96Nc1F PuUmUs14X8U79neL/4YrVvGf+wWyScs1qB2N4cT+/Rf4+sH3nonmPw7pzRNc1IvTh0KdNnKN/ qopZI1rjpXJ2Kr/UR0LfP2O2b2oz5PyShDirtn6Kas5OmoJstxBat6k4564bUyF1E2m2s5QVs uLiGg515vl36R2vuAfM9/HxVoSZosYhBcZx0/mL3gLd/jGdbX8IJIbxJ+Ba07sC9ppM7SEDv 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:151734 Archived-At: > The implementation of window-state-change-functions posted to bug#32672 > uses post-command-hook. It makes possible display-buffer-directionally, > e.g. S-M-up ffap RET will open a file link in the upper window, etc. Yes. But as I said in the thread for Bug#32672 running 'window-state-change-functions' only after a command gets executed may miss a number of important cases where the hook should be run as well. Once more: What could go posibly wrong if you added 'hook' to 'post-command-hook' and unconditionally (that is completely disregarding whether a buffer display action succeeded or not) removed the overriding action there. If you are paranoiac about this, you can even restore the old value of 'display-buffer-overriding-action' if and only if the new value (when running 'post-command-hook') is the one you wrote there ealier and leave any other value alone (because it was probably put there by the command executed). martin