From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: show-enclosing-scopes Date: Thu, 17 May 2018 16:24:08 -0400 Message-ID: References: <5cb3e5a6-310f-1f2a-ceb8-01b929158ebb@gmail.com> <594F9BDF-F041-4B8D-8425-0BE2AABAA448@gnu.org> <258be7dd-0bf6-f5b1-20d1-08ea65a177e8@gmail.com> <83wow2iamm.fsf@gnu.org> <83o9hehz3c.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1526588537 4628 195.159.176.226 (17 May 2018 20:22:17 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 17 May 2018 20:22:17 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 17 22:22:13 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fJPPg-00016q-1Z for ged-emacs-devel@m.gmane.org; Thu, 17 May 2018 22:22:12 +0200 Original-Received: from localhost ([::1]:34933 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fJPRn-00013B-83 for ged-emacs-devel@m.gmane.org; Thu, 17 May 2018 16:24:23 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52988) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fJPRg-000110-JE for emacs-devel@gnu.org; Thu, 17 May 2018 16:24:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fJPRa-0000Lw-7L for emacs-devel@gnu.org; Thu, 17 May 2018 16:24:16 -0400 Original-Received: from chene.dit.umontreal.ca ([132.204.246.20]:41599) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fJPRa-0000Jg-2i; Thu, 17 May 2018 16:24:10 -0400 Original-Received: from lechazo.home (lechon.iro.umontreal.ca [132.204.27.242]) by chene.dit.umontreal.ca (8.14.7/8.14.1) with ESMTP id w4HKOPEw015543; Thu, 17 May 2018 16:24:26 -0400 Original-Received: by lechazo.home (Postfix, from userid 20848) id 68F0E6049D; Thu, 17 May 2018 16:24:08 -0400 (EDT) In-Reply-To: <83o9hehz3c.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 17 May 2018 22:16:39 +0300") X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 2 Rules triggered EDT_SA_DN_PASS=0, RV6288=0 X-NAI-Spam-Version: 2.3.0.9418 : core <6288> : inlines <6642> : streams <1787028> : uri <2642956> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.20 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:225375 Archived-At: >> > I'd say if it is known that the goal point is not inside the visible >> > portion of the buffer after scrolling, don't scroll at all; instead, >> > just move point to the goal. >> I was assuming a situation such as a post-command-hook that wants to >> override the scroll that might have taken place during the >> preceding command. > No, the scroll command is part of the pre-command-hook set up by the > package. Or at least that was my understanding. Then indeed, most likely the better solution is to not scroll in the first place. Stefan