From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Po Lu Newsgroups: gmane.emacs.devel Subject: Re: Allowing point to be outside the window? Date: Mon, 07 Feb 2022 09:21:47 +0800 Message-ID: <87y22nlbdg.fsf@yahoo.com> References: <87ilwd7zaq.fsf.ref@yahoo.com> <83sfv85y36.fsf@gnu.org> <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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31140"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.60 (gnu/linux) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Feb 07 02:23:17 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 1nGskP-0007y6-5M for ged-emacs-devel@m.gmane-mx.org; Mon, 07 Feb 2022 02:23:17 +0100 Original-Received: from localhost ([::1]:54096 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nGskO-0003TU-5u for ged-emacs-devel@m.gmane-mx.org; Sun, 06 Feb 2022 20:23:16 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:57436) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nGsjU-0001wn-5Q for emacs-devel@gnu.org; Sun, 06 Feb 2022 20:22:20 -0500 Original-Received: from sonic309-22.consmr.mail.ne1.yahoo.com ([66.163.184.148]:36518) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nGsj8-0002CH-ES for emacs-devel@gnu.org; Sun, 06 Feb 2022 20:22:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1644196915; bh=yizqHXPTEnHBT6uJGhKhNiFc4ZK/t+X6ZxA7/aqQLsk=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From:Subject:Reply-To; b=M1UiBC6Q20WkQqlaDQlJeZl5Bs0GV3uidYhpNKIBv+YbTlOoXwtW3d0VUkhFA3gZrFQlDwJqiXTi8OgTPKzHTblZpHtyIVapCi8lCYioFQyBwmTTGZV1WizKqPitRolpawztJ3+CSWik9/YeNFtiQ0yL3+K0IM/AOD/sm4akd2XDqDzyt0pMQbiYn3LrZePmDrBoAOxdnTC82kqecarva6GrRppa0798HG4yorUEae0Warvv2n7gs6Qm9jE4C5GvDO8+yT6VLjY742VRFAiR23m5QZ9lgUWDa7zxYgvAFqaPo1k3ElPH5lu0ndvfXNmvXYb98KLRrjNzD0SY/b03wA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1644196915; bh=xr8gC7dYd/kgYbvzts2tEopPr2JAVeRWJKA78AGfA94=; h=X-Sonic-MF:From:To:Subject:Date:From:Subject; b=TiWSscziAEXlnyodW3wlOGEKL5Y1EW2n9hbSSSRQFOTDmR+xgckz79zNcPQkfzHgdwzZd2jsY+aMF1zaK/3iIFV+cxwSHwggw/bAEVFiS7nKdGvnXNcIEVUatz/SCoxXfBvFo4Dk5Nu/BVBzgPUddiQvbtbVM9sBxJdkypHOp58Z3xa5cPZ2Ntn5myTieBsXCVePDogtgFTCh7d+BPVsUPi5/FXE/JvtcuEyZXtTX8F8YAWSTp60ArE1MjL0gLnKeyNjORIinOir8w9+VUdN3Q+WqucyoDogjJupwI6Ne+6PVMmFwlH9z+n2C3VMfqKegZvdG2VkBM8jFv0sRROdGw== X-YMail-OSG: lUTiU_AVM1n0j_NFx1qm2ffanGExMU07yJW6fbdh7MY9oeo30Mh2Ux7Dy2c85zo 4Mpsh_Xkm438DPppl1XCLTXoM_HVuisy0PHtc6.BjTjzbVvAlbQ80WJt4elesooY5jiUFtidLuMr .Z3H_gD.1PVmywRrZP1F_vJfbogSIcoIaCyyqv_VdjkbkK3dY0HV99eqr_8BjGhrYW4w.KTVUPJL 3FWTgAu4afiZ.FJixq3ri6BPtBMsa3_4ul.P4e0pQZY_l9Qdd8s8BNnMZRz90fUV8gSyg1ugquYC Zy2_bGHgALEvJq6nzJGZSykUi4UrYwcaZ2IAhJ2BmDgyynM92sX1PsCuUJtqjset6q_9gkMCYX2d 9JdX._splGSRzo0qx5DPTzCG..M1ARkynz7vwaMWsWv0ZN5zjjmRHyP6uf0BOc2uGqIo1a7hLeL6 rniMK6faqv3WSvyUruT2G4dQcypky3WEL9nh0ZLPE4Wy4q3NdSN8Y6noIxF8T5pBIxdnHlEODiGX XDEotUxOnJUbhRqRxISVBeluGnvjdkPYhN9ttisj8nocwGaX2ZZziDi1uJIFOA.f0sTok8e7aYaW s.BgKM45kY13aR8pKYbTAM_WH61kvACNp_umn5HMHzE6xZnEmL_GgrAlOonjQvpYMXR7k6w0aGkT 4ywbuYKUvcfoO5ZyJcGJlE47W_gV4gP0RqQ9gm9zuOBbrAX1incYq5Hn3yxIBbqH232czw5FRIJo uNvnZRMHyljDQtXyb5vjvxY9NuKXaupAZksvB0swwqoYNwjlr.HqvJDxOAE6HL6milXbvdjgWyxw JFvM7OFb9A8mrwXJTxCyFtmBE2jxHThns2V3bTqzqe X-Sonic-MF: Original-Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.ne1.yahoo.com with HTTP; Mon, 7 Feb 2022 01:21:55 +0000 Original-Received: by kubenode516.mail-prod1.omega.sg3.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 67ddd4582192a09b0fa41aa0fd58dba6; Mon, 07 Feb 2022 01:21:51 +0000 (UTC) In-Reply-To: <8335kwynrp.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 06 Feb 2022 18:15:38 +0200") X-Mailer: WebService/1.1.19711 mail.backend.jedi.jws.acl:role.jedi.acl.token.atz.jws.hermes.yahoo Received-SPF: pass client-ip=66.163.184.148; envelope-from=luangruo@yahoo.com; helo=sonic309-22.consmr.mail.ne1.yahoo.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable autolearn_force=no X-Spam_action: no action 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:285999 Archived-At: 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? > For that, you must set the force_start flag. If you don't set it, > redisplay cannot know whether the value of w->start is just the result > of the previous redisplay cycle or was set by some user command which > wants to scroll the window. > > Perhaps you want to explore using w->optional_new_start instead? Yes, it seems to be perfect for what I need. Thanks. > Maybe so should we, at least as an option. Sure, an option would be nice.