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 05:02:41 +0100 Message-ID: <878rut6hlq.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> <87iltynkbg.fsf@web.de> <83h79i6iw6.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="30480"; 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 06:16:48 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 1nF80c-0007lZ-Pd for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 02 Feb 2022 06:16:46 +0100 Original-Received: from localhost ([::1]:47552 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nF80b-0005Kn-41 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 02 Feb 2022 00:16:45 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:51452) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nF6rS-00009N-2K for bug-gnu-emacs@gnu.org; Tue, 01 Feb 2022 23:03:14 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:57248) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nF6rG-0001Ud-Hi for bug-gnu-emacs@gnu.org; Tue, 01 Feb 2022 23:03:13 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nF6rG-0000ua-9c for bug-gnu-emacs@gnu.org; Tue, 01 Feb 2022 23:03: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 04:03: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.16437745723484 (code B ref 14582); Wed, 02 Feb 2022 04:03:02 +0000 Original-Received: (at 14582) by debbugs.gnu.org; 2 Feb 2022 04:02:52 +0000 Original-Received: from localhost ([127.0.0.1]:51145 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nF6r5-0000u8-QV for submit@debbugs.gnu.org; Tue, 01 Feb 2022 23:02:52 -0500 Original-Received: from mout.web.de ([212.227.17.11]:59029) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nF6r3-0000ts-Rx for 14582@debbugs.gnu.org; Tue, 01 Feb 2022 23:02:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1643774562; bh=aC9vZxQWHX/P1gJc9EtMxzbi17gYcvNwIvMz7++HJ+M=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=TXyibOWaOhZ1s4rnpb0VXbS+MtaZdulrLHtVFcIZXmOzjuxeGl1mVy2fW2d8jmMTM vvvGZg+izu3IgLwEA543/G73IQSFCoBQP1DiOV7iVGutu5KgNpvjM1y/3YTq36aZz6 wGyLDVFNQ+IS6P8fWF/RES9Xttdb0j2ONcgGwETA= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Original-Received: from drachen.dragon ([84.57.248.31]) by smtp.web.de (mrweb106 [213.165.67.124]) with ESMTPSA (Nemesis) id 1N5lj7-1m8u8f2cQd-017HZG; Wed, 02 Feb 2022 05:02:42 +0100 In-Reply-To: <83h79i6iw6.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 02 Feb 2022 05:34:49 +0200") X-Provags-ID: V03:K1:lD8VtsagN1V++L2I8SB6ruZ+pOTCTVh8tGFxJSUK7qU8vlVSUJR mZUz5BIStpehhSsNx4YVnY3y0GnPCJ+XfnmOIJ9iFpUkQKeYMa1NVPidUPhKvUGj959KxTJ Wq2rHN4AkVTP3RyoLJedUTBZ57nCtuB0ZR6KsbghAwHImC96jotYvPB3ONDWxft/GMMj5MW k4WpKauLbd/qJWXMTYmbA== X-UI-Out-Filterresults: notjunk:1;V03:K0:aAIqL18trvg=:dZYNzTLq0O+IFCVnH1uA2M NLqNNigVIIKJiU4A2e/5VC+8pfdlyaJpPZmTj0hjGgYhTLcCBBL0IHwFGYEa4i7sG56UwAklz fcoJJ6eK1lV+olUkTwpJ1a+tvcouFn3f7NhdiG9r+V8HsRBtJPqOp5fBykmFBo/2cBhjilx7T NV3lMtJBDiqho8b5pjXkOLmDSi64A3njRq7iSkObT4gWwovX0EpbqyGR3MpWJLIw7hU+PNCXF 9kAlRuw1ylxDpiCAirco4HLAufudOa3C9dTKlIRpTtfzvOy56CnGFJPZffNftgvxdcs3y61pC pV8mEcdFavviUu7QwseDmu2NdD2Vp8YHrsR6HCPRccpIW4aZ1KXPykUojuezy73L9ikXG6SoF Uy7CVN+9BIjCbvGgIzsyP4iQZQcfu8Q4/HRMRMkWGCVgDC7ehTRGVxevXJxh/dm0JPrlhdnM0 0FQMdjBAHPy7TpYikfi+B3PzaY1l+ffiYREeAqP6aCaNoZBWNQc7wpcJa8Zku4XQj/pjIoUdt XBPvDjtV7fQOZXuUMFH5xQ6D01HfMdDDY2iHg2AJjBWbIxX8ik5muzh41BBkUVxH+HyG8WjBc O2bDe0iHrlKu7eYYc/u71pILni9WXIoW4Vb6AsRFAwXQ7OPgpGz+cidK6gox+tQbTymBReOpn ZqXcn1C3KtN/OVkpNICmD15d3Jg9hvXEgvaCIEIALz0c1YBitRDZqGkm+R9nP4DfmpvS6UnzY MtNJWw5aPTBEQrYst1jwqmOlwY4JJUGtMdBCw8Lkq+JU82kf3DLsIcATY0JcQwk0a2BeMWA7 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:225783 Archived-At: Eli Zaretskii writes: > How can we know? There's any number of Lisp programs out there using > invisible properties. Starting with Org. In Org I actually see the same bug (I tried org-shifttab). Isearch also has the issue when re-hiding opened invisible text areas. Could be that in most usage scenarios the current behavior is not wanted. > > Why can't the credo just be "always ensure complete visual lines are > > displayed"? > > Because a Lisp program may wish otherwise. I do know and only know Lisp programs that wish like this. It feels wrong that Elisp programs should have to adjust window-start. Anyway, no surprise that I see it like that. Is there a third alternative, a hook or something that could be used, to perform this task automatically? I mean, else, every program that toggles invisibility of text would have to loop over all windows that display a certain buffer, examine text properties and check whether window-start has to be adjusted. I would not even be sure what to do in situations when the first line is only partially visible and such stuff. Michael.