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.devel Subject: Re: Allowing point to be outside the window? Date: Mon, 07 Feb 2022 15:41:12 +0200 Message-ID: <83fsouyetj.fsf@gnu.org> References: <87ilwd7zaq.fsf.ref@yahoo.com> <87v904tsvv.fsf@yahoo.com> <83h7bo5m1x.fsf@gnu.org> <87ilw3ubfp.fsf@yahoo.com> <83h7bn4e55.fsf@gnu.org> <877dcipjmk.fsf@yahoo.com> <83mtld254e.fsf@gnu.org> <87lf0xjgxu.fsf@yahoo.com> <83ilw0zg38.fsf@gnu.org> <87mtlbgajq.fsf@yahoo.com> <83czm7vx0s.fsf@gnu.org> <87mtlad3sv.fsf@yahoo.com> <83mtlaurxj.fsf@gnu.org> <87fsqh9o7s.fsf@yahoo.com> <878ruoqx0u.fsf@yahoo.com> <83h79cz0sm.fsf@gnu.org> <87leyonrp4.fsf@yahoo.com> <83fsowyzt9.fsf@gnu.org> <87pmo0mbig.fsf@yahoo.com> <8335kwynrp.fsf@gnu.org> <87y22nlbdg.fsf@yahoo.com> <87v8xri1ki.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3312"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Feb 07 15:11:48 2022 Return-path: Envelope-to: ged-emacs-devel@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 1nH4k8-0000im-IF for ged-emacs-devel@m.gmane-mx.org; Mon, 07 Feb 2022 15:11:48 +0100 Original-Received: from localhost ([::1]:47374 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nH4k7-00032o-Dy for ged-emacs-devel@m.gmane-mx.org; Mon, 07 Feb 2022 09:11:47 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:45758) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nH4Gn-0004lZ-P4 for emacs-devel@gnu.org; Mon, 07 Feb 2022 08:41:30 -0500 Original-Received: from [2001:470:142:3::e] (port=51030 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 1nH4Gn-0005lJ-FK; Mon, 07 Feb 2022 08:41:29 -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=RZNLGLOkNfxCrAWHnbGbJMKdqTebq7HojkMUZfNl7AU=; b=rjwU3t821txI FbhOJ7iSFunVm/iNWO1y8Vd11nDRRaj0Bfo3vkI8ITy19OvDSTtPbQsPJdV9+iVI7RUWxclrujKy2 1U17HNAmC12mTlyjvP5PzQ9xXK/NLh+hO1ZsBYVYvJgqSdpc6JtNx5KIj8n3HQbc2TGhTXpF7qDer FsTum0MO9h+A0a10oUh5iCafX58nE4MJ/ZjLVZir0sDk3+hFK7kFxmPes9Cj7JEug4+b1GmJZu0+L GZj4+Sj7G1emZPrHbYm0t4hhxTlk1eYfagdZg2QxYtx6LXmgRoothh9rgME1mMQ5QRbKgKKvRfR1/ KO6SAc1rXvHkFkTvVEN3Ug==; Original-Received: from [87.69.77.57] (port=3981 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 1nH4Gl-0004Zf-0S; Mon, 07 Feb 2022 08:41:28 -0500 In-Reply-To: <87v8xri1ki.fsf@yahoo.com> (message from Po Lu on Mon, 07 Feb 2022 15:21:49 +0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:286046 Archived-At: > From: Po Lu > Cc: emacs-devel@gnu.org > Date: Mon, 07 Feb 2022 15:21:49 +0800 > > Po Lu writes: > > > Eli Zaretskii writes: > > > >> So we have at most 3 states, and could have a single tri-state > >> variable. > > > > Indeed. > > > >> And I question the validity of the combination scroll-move-point = nil > >> with keep-point-visible = t. The problem with your implementation is > >> that scroll-move-point = nil disables scrolling in redisplay_window, > >> but scrolling there is used not necessarily as result of scrolling > >> commands, but also when redisplay_window decides that the optimal > >> method of updating a window is to scroll its previous contents. Thus, > >> disabling scrolling on that level will cause confusing results, > >> because users will expect that to affect only scrolling commands: they > >> are unaware that redisplay sometimes scrolls the window for other > >> reasons. > > > > Perhaps we could have redisplay bind `scroll-move-point' to a reasonable > > value before calling the scrolling commands? > > I don't see where the scrolling commands in window.c get called from > `redisplay_window'. I didn't say redisplay calls the scrolling commands: you did. The truth is that redisplay doesn't call any scrolling commands. > Is it try_scrolling? try_scrolling is not a scrolling command, it's one of the methods used by redisplay to update a window's display by reusing parts of the existing display.