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 16:24:46 +0200 Message-ID: <83a6f2ycsx.fsf@gnu.org> References: <87ilwd7zaq.fsf.ref@yahoo.com> <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> <83fsouyetj.fsf@gnu.org> <871r0eg4o1.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24056"; 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 16:00:45 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 1nH5VU-00068A-Bs for ged-emacs-devel@m.gmane-mx.org; Mon, 07 Feb 2022 16:00:44 +0100 Original-Received: from localhost ([::1]:44770 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nH5VC-0002Pr-C8 for ged-emacs-devel@m.gmane-mx.org; Mon, 07 Feb 2022 10:00:28 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58520) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nH4wu-00052r-RV for emacs-devel@gnu.org; Mon, 07 Feb 2022 09:25:01 -0500 Original-Received: from [2001:470:142:3::e] (port=52836 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 1nH4wu-0005sE-Ek; Mon, 07 Feb 2022 09:25:00 -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=X0xRxdQEb+RIXGlWG9VF7PGL6+aXeX7i4LKSK2Lv5qk=; b=q5fl10Gaii6h lmL2uRAhEV9oLurboh0FepKvLc+q9GS1eKGPnKyTwrmSaDIu22Irw4Rt3xCGPBPKS0V/eBJSdihYL LH9hnd8WTJQPD8/S5vmFGs8PXTYZTdaHbcu+vfMO0axUfrSDIBfNyewjAuiC07e33p4ZLdPRHa5ik rMQ6XgW52ZbxSRxxdTAQwRYqIemDkhJ9lbsLQmRB4MxlRoUc2OjckaNWgAwN0C8gRfVwmUTY2lBR4 JTQEQS2R3Hw1K2k5B63KRQi291FOM8Ah76BQAYcmppm7Xtrl/0wdOiitIQBIz1ej5HGxyiEk+lyGz WfhdsvgnUCptUqiJ90Tp9A==; Original-Received: from [87.69.77.57] (port=2675 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 1nH4wt-0008Na-Ut; Mon, 07 Feb 2022 09:25:00 -0500 In-Reply-To: <871r0eg4o1.fsf@yahoo.com> (message from Po Lu on Mon, 07 Feb 2022 21:57:50 +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:286053 Archived-At: > From: Po Lu > Cc: emacs-devel@gnu.org > Date: Mon, 07 Feb 2022 21:57:50 +0800 > > Eli Zaretskii writes: > > >> >> 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. > > > I didn't say redisplay calls the scrolling commands: you did. > > > > The truth is that redisplay doesn't call any scrolling commands. > > `scroll-move-point' doesn't affect redisplay; it only affects the > scrolling commands in window.c. It does affect redisplay: by not setting the force_start flag of the window. > I thought what you wrote was a typo, and that you meant to say "disables > scrolling in window.c" or something else similar. No, the problematic word was "scrolling": I meant the large block in redisplay_window conditioned by w->force_start being non-zero. That includes the code under try_to_scroll.