From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#35860: Delayed window positioning after buffer display Date: Mon, 17 Jun 2019 10:23:18 +0200 Message-ID: References: <87o93ucjsi.fsf@mail.linkov.net> <83ef4p7prf.fsf@gnu.org> <87a7fc51qm.fsf@mail.linkov.net> <83k1eg5pmx.fsf@gnu.org> <87k1efhkgp.fsf@mail.linkov.net> <2347769f-9ab3-c1b6-699e-4e89a7d8eb1c@gmx.at> <875zpb4zdw.fsf@mail.linkov.net> <878su5i67f.fsf@mail.linkov.net> <87muik3svu.fsf@mail.linkov.net> <4d0733b1-4ee0-222b-395a-8f26ff76f2da@gmx.at> <87imt6jva7.fsf@mail.linkov.net> <87h88p8e5z.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="143829"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 35860@debbugs.gnu.org To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Jun 17 10:24:19 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hcmw5-000bGJ-3s for geb-bug-gnu-emacs@m.gmane.org; Mon, 17 Jun 2019 10:24:17 +0200 Original-Received: from localhost ([::1]:45072 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hcmw4-0001Sr-5Y for geb-bug-gnu-emacs@m.gmane.org; Mon, 17 Jun 2019 04:24:16 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42204) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hcmvt-0001Rx-H1 for bug-gnu-emacs@gnu.org; Mon, 17 Jun 2019 04:24:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hcmvq-0002AV-EB for bug-gnu-emacs@gnu.org; Mon, 17 Jun 2019 04:24:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:56588) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hcmvp-00028y-R6 for bug-gnu-emacs@gnu.org; Mon, 17 Jun 2019 04:24:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hcmvp-0002C4-MX for bug-gnu-emacs@gnu.org; Mon, 17 Jun 2019 04:24:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 17 Jun 2019 08:24:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 35860 X-GNU-PR-Package: emacs Original-Received: via spool by 35860-submit@debbugs.gnu.org id=B35860.15607598078389 (code B ref 35860); Mon, 17 Jun 2019 08:24:01 +0000 Original-Received: (at 35860) by debbugs.gnu.org; 17 Jun 2019 08:23:27 +0000 Original-Received: from localhost ([127.0.0.1]:41899 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hcmvH-0002BF-Ek for submit@debbugs.gnu.org; Mon, 17 Jun 2019 04:23:27 -0400 Original-Received: from mout.gmx.net ([212.227.15.19]:37613) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hcmvG-0002B1-60 for 35860@debbugs.gnu.org; Mon, 17 Jun 2019 04:23:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1560759796; bh=G+6Xgc6Pmx9/LtX3k4eV9iyLIx+sJmTDIVR41aRLIMA=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=OZVeNHLaz5g7SuYdimL442ytvulZ3TFiotzh2oI0BFHnJjslYlGMQzpkGOx+sWtQU unIoUZ0MKtXtBoLJYtC9oGX1roT+Dz+0TOjOz8Z+gUp8WypA6KcurA4FTwvzqERzqD 07iXtHG+Bi7t43J/wTg4U54OlOvdmkCeRLFDhu94= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.101] ([212.95.5.18]) by mail.gmx.com (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1M4JqV-1hcVnx1AOH-000JGB; Mon, 17 Jun 2019 10:23:16 +0200 In-Reply-To: <87h88p8e5z.fsf@mail.linkov.net> Content-Language: de-DE X-Provags-ID: V03:K1:qbbYKBeKnbzU0lC0Qfmvno4HGw5nnYP1s7/g0xAxyqu+Xp0fTLA 1UpoYW7gbPGHjoNhUl5+0Q2Tz0vz0IrIYNPC+HoSZL4evw1Azts8v2ZYftb2r3FxA+TWEsn HSbO/2ZhoGD+bSNRqDNyNroTiiOPH43tKTDPzaqb/ReufU5YZP6wRXWS6/HppOnax+IXB5G kWXrufkqdEhwYzgdX5JGw== X-UI-Out-Filterresults: notjunk:1;V03:K0:KHfBP0mCoto=:J3Y1kM6SOe8SrGMY9NekiU 4s00gr4cDTRjClMrfke32YgMz0aZ1Q6GRH2lm95Q7Oz+zGLxP2yL+FTn237LqdtpgIa0cvkv0 /NSIgTPveRf9/7QVuH/uNbemRB1/CpDexOcV6jL2RoSdoy3iI46srtllIE2CXI0x5JWnhI3gz fa6vuCxwSZp9ndrzZvKgv4j0Ew1WKX45yhDbn7QNmkHfVzxbngjV0hW7sf1OK+kosbE4oPR+G rcWevmOlvRf+nFyzRh9G+BIC2K3fxAe5AEUW3JxK9uUS0zjPtbzU+DNpXJ6cmBITzdyUQuGR2 cfY7y+v+Skq2UgD5OaA+aJZgCtVs2oiZDNeItmEaJ4mEBwy0mM9wZAt7QzUX0b4qSFkHGUI4n ALgA+z7Kxxe+RENr4cCv/mXnZcUD1m9cnjfVciVA9IozsSwZYAdwmiBWW2wgckfxnWZnCLi6b SdU8YExqS+txCd6YL2O2/WNkaMfVoUaw9niBxguQqe0M8BOD6msc0rdZsdf9vq6CRms0nnYS+ 1saDRupcn3NvubU/RxxR2Y/RiwX3gEr/+oCfyT6mRt6Oo/KVi2FIuDa7guU8n2qaVD5l0d+jo M+JBCyBSpd0a+DDkUwLAH3FCBognTb4ejzmdLXJkCA3OBWzMJBvHUdDOwNF0gbwfvOju1aCbR Md/Q0v5HKWjF8phvFgp+qKYY/A61U9GbNkQBlFybWSPCitZBAKgOVr171EivK0rVhV1Iey0pR Asqk5sMQkz0sAUvvopjCgwGk7QJa4XkYQa+DURVGnrKZc7qSNyeV66CNZWdyzk09nWtVD3gJ 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: 209.51.188.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:160715 Archived-At: > BTW, there is a strange comment before the first line: > > ;; Don't try this with NOFORCE non-nil! > (set-window-start window (point-min) t) > > but its NOFORCE is non-nil here. Is this a FIXME-like reminder? Rather a FIXME-like remainder. I probably did try to fix something here but don't recall any more if the comment applied to the version before that fix or should apply to the present version (in which case it is obviously wrong). > In my previous patch there is no need to check for the buffer, > because a new general variable is declared as buffer-local. But the BUFFER argument of 'window--display-buffer' is not necessarily the current buffer. Or do I miss something? >> What happens with these markers when 'display-buffer-no-window' gets >> called? Or some user provided routine provokes an unhandled error? >> You don't even check the marker buffer of these variables so some old, >> completely unrelated marker could get reused here. > > There is no global effect because this feature is localized > to a single buffer by its buffer-local scope. We would always have to assure that the marker's buffer and the current buffer are the same. And we would have to make sure the marker gets reset when an unhandled error occurs. > We could support an action alist too in addition to buffer-local variables, > but we should leave an ability to set buffer-local variables, because > neither view-lossage nor vc-git-print-log (two primary cases to test > this feature) have no access to the 'action' arg of display-buffer. Maybe we could provide a new macro which encapsulates the use of these variables in a more disciplied fashion (providing the necessary action arguments for `display-buffer'). martin