From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#14582: 24.3.50.1; Strange overlay behavior, when window-start is inside an overlay. Date: Sat, 12 Feb 2022 09:28:28 +0200 Message-ID: <83fsoosfvn.fsf@gnu.org> References: <83pmo678o1.fsf@gnu.org> <87iltynkbg.fsf@web.de> <83h79i6iw6.fsf@gnu.org> <878rut6hlq.fsf@web.de> <83czk578m0.fsf@gnu.org> <837dab4zmm.fsf@gnu.org> <875ypvcsyf.fsf@web.de> <83k0ea3fci.fsf@gnu.org> <87r18gn1rh.fsf@web.de> <83k0e8z3uo.fsf@gnu.org> <87k0e6xkta.fsf@web.de> <83v8xqvxox.fsf@gnu.org> <87r18ej957.fsf@web.de> <83r18dwnqn.fsf@gnu.org> <875ypor90e.fsf@web.de> <83wni4up6g.fsf@gnu.org> <87pmnvr0l4.fsf@web.de> <83a6ezuu00.fsf@gnu.org> <87wni2ypx7.fsf@web.de> <83tud5ssd4.fsf@gnu.org> <87bkzdj5h3.fsf@web.de> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31805"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, esabof@gmail.com, 14582@debbugs.gnu.org To: Michael Heerdegen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Feb 12 08:29:23 2022 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 1nImqP-00085J-WB for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 12 Feb 2022 08:29:22 +0100 Original-Received: from localhost ([::1]:59194 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nImqP-0005oy-40 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 12 Feb 2022 02:29:21 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:49782) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nImqA-0005oZ-Bh for bug-gnu-emacs@gnu.org; Sat, 12 Feb 2022 02:29:06 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39397) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nImq5-00089r-Qy for bug-gnu-emacs@gnu.org; Sat, 12 Feb 2022 02:29:05 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nImq5-0004Li-K1 for bug-gnu-emacs@gnu.org; Sat, 12 Feb 2022 02:29:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 12 Feb 2022 07:29:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 14582 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 14582-submit@debbugs.gnu.org id=B14582.164465092416691 (code B ref 14582); Sat, 12 Feb 2022 07:29:01 +0000 Original-Received: (at 14582) by debbugs.gnu.org; 12 Feb 2022 07:28:44 +0000 Original-Received: from localhost ([127.0.0.1]:33294 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nImpo-0004L9-Ic for submit@debbugs.gnu.org; Sat, 12 Feb 2022 02:28:44 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:43020) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nImpm-0004Ku-Ja for 14582@debbugs.gnu.org; Sat, 12 Feb 2022 02:28:43 -0500 Original-Received: from [2001:470:142:3::e] (port=58874 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nImph-00088W-1m; Sat, 12 Feb 2022 02:28:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=YAvCZscDYJbcjmn3S31Xyub6hKOONDu5J3Jge9stvrc=; b=rkZs90xmY79Q ZQUu8HEaWWojAMTTQjtOzW/bZzMV+MulowM4ZzhpPPuzeYZX17rgKtmOpqkpFPk7ve16s6qduXtyM 72He+bCGIOsmzmcCXBl9vFH3IB/PP77AKsOqF1Uf80CCNFkFF5ENXH6r/fyD9yUD7wbamS1H2Qpnh P/P0y+g/V3/lq9TviUE2aBxXQpFNwiwE38Rldcx3v1Bd0X3u9+WA5QVKWumGJgO8CRHXaodGXjPwD w6U2DExygbmvMzNaNbgrMp774t1Qmt/AJUe4M1ddcuycHsaD/vWfykVMUIj2vnk1YUwqjT788S+Jc CqOA596WFMLstrHSPpkHvw==; Original-Received: from [87.69.77.57] (port=1574 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nImpg-0008EW-Dc; Sat, 12 Feb 2022 02:28:36 -0500 In-Reply-To: <87bkzdj5h3.fsf@web.de> (message from Michael Heerdegen on Sat, 12 Feb 2022 01:25:44 +0100) 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:226699 Archived-At: > From: Michael Heerdegen > Cc: larsi@gnus.org, esabof@gmail.com, 14582@debbugs.gnu.org > Date: Sat, 12 Feb 2022 01:25:44 +0100 > > Eli Zaretskii writes: > > > Once again, this option was intended to be used in relatively rare > > situations. I do not recommend to set it by default, especially if > > the side effects annoy you. > > Ok, finally I understand now that the display engine can't do what I had > in mind. > > IME folding can confuse the eye, and the vertical position of the cursor > is one of the main visual anchors - I would want to avoid any scrolling > involved to solve this bug. Which would mean a fix is yet to be found. I disagree. The fix for the problems originally reported here was found, and it so far solves all the use cases presented here that involve either folding or selective-display. The fix handles the potentially confusing display when folding or selective-display settings are changed so that the previous window-start point winds up being hidden. After the change in folding or selective-display, and as long as these settings don't change, the window-start point is expected to be visible at all times (due to how window redisplay is done, something that wasn't changed by the changes in this bug report), and thus no unexpected scrolling should happen. The use of the new variable in all buffers is not recommended, and not what it is supposed to support. In particular, its use in Info buffers may cause unexpected side-effects. Since display in Info buffers is fine without this variable, I don't see how what you get there is any evidence of a missing fix. A fix for what problem? Bottom line: I think this bug should be closed, as the original issues were all resolved. If you disagree, I guess I'll let Lars close it in about 10 years from now.