From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.bugs Subject: bug#14582: 24.3.50.1; Strange overlay behavior, when window-start is inside an overlay. Date: Wed, 02 Feb 2022 02:12:03 +0100 Message-ID: <87iltynkbg.fsf@web.de> References: <83y5ajmcwk.fsf@gnu.org> <83sj0rmat2.fsf@gnu.org> <83r4gbm991.fsf@gnu.org> <87czk87vmo.fsf@gnus.org> <87k0egwxk6.fsf@web.de> <83k0eg7y23.fsf@gnu.org> <87sft37nmo.fsf@web.de> <83a6fb90zy.fsf@gnu.org> <87h79j2srb.fsf@web.de> <83pmo678o1.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18807"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: larsi@gnus.org, esabof@gmail.com, 14582@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Feb 02 04:04:03 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 1nF5wA-0004k6-Mt for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 02 Feb 2022 04:04:02 +0100 Original-Received: from localhost ([::1]:36844 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nF5w9-0001g6-Ht for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 01 Feb 2022 22:04:01 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:47660) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nF4Cl-0001Gf-CJ for bug-gnu-emacs@gnu.org; Tue, 01 Feb 2022 20:13:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:57067) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nF4Ck-0006HX-Qe for bug-gnu-emacs@gnu.org; Tue, 01 Feb 2022 20:13:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nF4Ck-0004cc-BL for bug-gnu-emacs@gnu.org; Tue, 01 Feb 2022 20:13:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Michael Heerdegen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 02 Feb 2022 01:13:02 +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.164376433217700 (code B ref 14582); Wed, 02 Feb 2022 01:13:02 +0000 Original-Received: (at 14582) by debbugs.gnu.org; 2 Feb 2022 01:12:12 +0000 Original-Received: from localhost ([127.0.0.1]:50964 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nF4Bw-0004bO-Kl for submit@debbugs.gnu.org; Tue, 01 Feb 2022 20:12:12 -0500 Original-Received: from mout.web.de ([212.227.15.14]:47721) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nF4Bv-0004bA-IE for 14582@debbugs.gnu.org; Tue, 01 Feb 2022 20:12:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1643764324; bh=Pu4dhiiBu8t7BmYGheWsDPzPRemlmJQFWaWP4uoIxk4=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=erNZcapED/R6FEAXdr2KfRdVdv1j3PM5XMpys91IeWUWVS4VLg7KvzV3w0Nm8T20o AWX1YAEdY6EoQV/HSih12JiwFwlqZCCJxymobxERBWbrJZe7LODRycfJP0QajAYMHm +3BNlMHIlj0ZTIJI0SVEsT2HvySXlTbGvgqttmvE= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Original-Received: from drachen.dragon ([84.57.248.31]) by smtp.web.de (mrweb005 [213.165.67.108]) with ESMTPSA (Nemesis) id 1Ma0PY-1mlJxI2lJk-00WEaN; Wed, 02 Feb 2022 02:12:04 +0100 In-Reply-To: <83pmo678o1.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 01 Feb 2022 20:18:06 +0200") X-Provags-ID: V03:K1:JNls/SUkl51r+ann2kw3OxoRnSFZyVmrs+AQpRqceI8ehiZTyrM HvfFZhUEhjb6W3q7HYnSwl09pG6YCQahkHjxgPo1toD6bzHCJrQuqsosDKza/nmVASBKO2c gzvCZq7KCOJBC+LbGV5y1fmehJdO8i8kQl1o8Z//fSUrqHWf2HBJU3Pmz9nQfGcG3YYqCm1 aRDwWuvIV8HPZd+gPxyYQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:fTn4t0IWPfQ=:aia6NNedWY6Akp0lW8k//J rAAAf+mdU59FDRqg3Sob2GtTUE1gv7ZqyXMD3utFA4AFpYXZS+vOUEnDT8X4U/kQeAiDR4LHV Sc4c62u3dF+J8o/Bc9j9hfuHLVWxMb6GMyg6xASHRn1nG5/+IWddryypklSJr1l58QDnlG11D BhhStqyAEj9LWdhGJTqTO4bc9HG9VvMX/5QYDA9cBG6CMzQaUbvM/2dGVXphL94luNTbK3I83 Q9hgVgNb0jYo7SWzkoxRAf4/VCbbxoXrSUwqtJA/ZRHnbt6dPy1oEoDwHyoY9h2xdJBOqRY4Z 83NPhxTcYjqFHqA9h3qZVq9oQTyXQlqTxRA7Kya6M0lLds2uLdS5T/AZAalAEMPd8Qr47UoKT NE+g31Yhel5+tAHustN7u6/ZBd1fkF8gdb3jjhGUYIJJvJbTmNtKn9D4VfMUTB9wT+/8wD7Lm C4NFVh1Adu6TUs5pLo7j4it8JC4379rcBftxDCGs6fXP0Px+HRPEBqIZHjJgkDoTgMP3dsVxx NpFnQ4shA0WYmrSAzGjyQ6OtlVWOYKDwotZDARID/9ZaCTCAdGDVF6srqWLiRM9bmt/vjyBN0 fsx4NDAVMiFgiksd9shjLszBdFnhE+2ZDUQkGgxxWJijCMaqilMOJO1VpZqvutaZnVsL59JSu M/xgY93FsfiLaBs7Ii6o9Y8DJgUeK/UuzXH9ByzBqZq0LBACxgZ/vMWV9DN/R+COkEj21mf3e moO2u213uUavhw3XxG28BIIH1rluV5/BKQZ/EaHQ5CjGcY7aC9SWF0YcLISPmCj/zJ1UP4jw 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:225772 Archived-At: Eli Zaretskii writes: > Perhaps your mental model of redisplay is that it determines the > window-start position _after_ it applies the various text properties > and overlays, which affect what will be visible on display. In which > case it would have noticed that after hiding the function bodies the > visual line will start at "(defun ...", and would therefore start the > window's display there. Yes, something like that. At least, I would not expect that only a part of a (visual) line is displayed, however that comes. > hs-minor-mode _does_ know what effect it wants to produce, so it's > hs-minor-mode that needs to adjust window-start if it happens to wind > up in the part of text that is about to be hidden on display. Let's extend the discussion to invisible text in general - hideshow is only one application of invisible text. Are there cases where the current behavior makes sense and is expected? More sense than the behavior I expect? I ask because you said that the display engine can't know the intention. Does it have to? Why can't the credo just be "always ensure complete visual lines are displayed"? Regards, Michael.