From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Spencer Baugh Newsgroups: gmane.emacs.help Subject: Re: Make scroll-{up, down} move point to {start, end} of newly visible text Date: Tue, 01 Aug 2023 10:45:07 -0400 Message-ID: References: <9d0b82c3c7bf738c47472fa908ad70daa3e9eced.camel@adminart.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18678"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:KggFSPxtg8zb7bxHkPos+aGW7u4= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Aug 01 16:46:05 2023 Return-path: Envelope-to: geh-help-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 1qQqdR-0004aV-85 for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 01 Aug 2023 16:46:05 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qQqcj-0007Cr-Em; Tue, 01 Aug 2023 10:45:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qQqch-0007Cb-GO for help-gnu-emacs@gnu.org; Tue, 01 Aug 2023 10:45:19 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qQqcg-0006Pu-2X for help-gnu-emacs@gnu.org; Tue, 01 Aug 2023 10:45:19 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qQqcd-0003R3-UP for help-gnu-emacs@gnu.org; Tue, 01 Aug 2023 16:45:15 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=geh-help-gnu-emacs@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:144528 Archived-At: hw writes: > On Mon, 2023-07-31 at 16:18 -0400, Spencer Baugh wrote: >> After I use scroll-up or scroll-down, I want to start reading the new >> text on the screen. But it's easy to lose track of where the new text >> start, especially with larger values of next-screen-context-lines. >> >> So, I would like scrolling to move point to the division between old and >> new text. Then the location of the cursor will help me keep track of >> which text is new and which text is old. >> >> Concretely, this means scroll-up should put point at the beginning of >> the new text (and therefore at the end of the old text), and scroll-down >> should put point at the end of the new text (and therefore at the >> beginning of the old text). >> >> Is this possible? > > Maybe try the following: > > > (setq scroll-preserve-screen-position t) > (setq scroll-conservatively 0) > (setq scroll-margin 1) > > > With this, I can see point and that is where the text scrolls to. No, I don't think this does what I said at all, I'm afraid. >> Alternative suggestions for how I can keep track of what text is new on >> screen after scrolling are also appreciated. >> >> I think I only want this for scroll-{up,down} and >> scroll-other-window{,-down} but possibly it would make sense for other >> commands which I don't know. >> >> (I would file a bug requesting this feature, but scrolling is so >> fundamental that perhaps this is already supported by some combination >> of features which I don't know) > > Have you tried scroll-lock-mode? Yes, it's nice, but I also want the normal scroll-{up,down} commands to work. I think scroll-lock-mode could do with a more convenient default binding, also. A lot of programmers, including me, have keyboards which don't have a scroll lock key...