From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: William Rankin Newsgroups: gmane.emacs.bugs Subject: bug#39967: 27.0.90; how to debug point moving erratically? Date: Tue, 10 Mar 2020 20:29:09 +1000 Message-ID: References: <831rq4bnmc.fsf@gnu.org> <813C2B33-3356-4E32-A50D-4D4B9D2B3C74@bydasein.com> <83r1y4a0it.fsf@gnu.org> <83mu8s9uw2.fsf@gnu.org> <9AB559B6-102A-4805-B7A1-55FB0195C9E2@bydasein.com> <83eeu49o48.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="25065"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.2.0; emacs 27.0.90 Cc: 39967@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Mar 10 11:30:19 2020 Return-path: Envelope-to: geb-bug-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 1jBc9S-0006OF-TI for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 10 Mar 2020 11:30:19 +0100 Original-Received: from localhost ([::1]:56826 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jBc9R-0002eK-QB for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 10 Mar 2020 06:30:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34095) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jBc9E-0002bY-Uk for bug-gnu-emacs@gnu.org; Tue, 10 Mar 2020 06:30:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jBc9D-0000Pd-Qw for bug-gnu-emacs@gnu.org; Tue, 10 Mar 2020 06:30:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:45948) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jBc9C-0000Lg-GZ for bug-gnu-emacs@gnu.org; Tue, 10 Mar 2020 06:30:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jBc9C-0007oM-BN for bug-gnu-emacs@gnu.org; Tue, 10 Mar 2020 06:30:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: William Rankin Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 10 Mar 2020 10:30:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 39967 X-GNU-PR-Package: emacs Original-Received: via spool by 39967-submit@debbugs.gnu.org id=B39967.158383616629957 (code B ref 39967); Tue, 10 Mar 2020 10:30:02 +0000 Original-Received: (at 39967) by debbugs.gnu.org; 10 Mar 2020 10:29:26 +0000 Original-Received: from localhost ([127.0.0.1]:51921 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jBc8c-0007n7-8B for submit@debbugs.gnu.org; Tue, 10 Mar 2020 06:29:26 -0400 Original-Received: from wout3-smtp.messagingengine.com ([64.147.123.19]:58697) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jBc8a-0007mo-0D for 39967@debbugs.gnu.org; Tue, 10 Mar 2020 06:29:24 -0400 Original-Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 45C2A934; Tue, 10 Mar 2020 06:29:18 -0400 (EDT) Original-Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 10 Mar 2020 06:29:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bydasein.com; h= references:from:to:cc:subject:in-reply-to:date:message-id :mime-version:content-type; s=fm2; bh=uVhnb6n65hfvKg7dZXQ2K3Z6Xf JEpiMo/cMmgzmS4Rc=; b=PXsDuaFIkppSKtqmuQO2BDslxGXgNNyJdP7GslofK3 dZ+Jj+30odB3YGdUcvDzBlglYvdQDufOJKWlp1XSWkwGrpQKERr5FL7Nxl/CShN/ 6vJshS54tsxWrDEicLg4IhHOJ/iY6Fw4nNguMGC80LBBoo2rSzL/vRB1l5mxLWvc wyHZFFqVWEYk0hd0HjN077/24iw5g7H50uRZiQyUou8U9Pk8hKSpOjNZS2C2gIhi x0imWI/hlXceOOM/kH0VgLJuiGwtl7PQNND18NfQyDfNDa965x6bYOvzTfH4k3LT lrvZeKmqpgynRmzdSoNs83mzDHObZjtUEsqTfV7achAQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=uVhnb6 n65hfvKg7dZXQ2K3Z6XfJEpiMo/cMmgzmS4Rc=; b=sKNcxNroicsxKWHrHxJlMI XgSRetX8pvj13SB5xq5FbhRF1adkcxIxq88S1bF6dbn/bXPBXvuBX6+EiOxOMKbD q1+hUlT8C2uYABxheusZCZisNAgeNElx8t4HzRupv7Nq0FxN2Ccdws3KnOMC1rjH MpKHdMpw0A6EgxK0Enj3y8vfXxNHO14yPGJ8SfRguJGCOdm6AGJ+1m8ftpYmy9Nc zafukDN5j7s1u6xtmlArFb+hdb+Bs9MaP8gRR0YElAUTp70GhzxXzeZ4c93N9+wp Iul2a+0bFgcfov8IY6Z+NdKLjromrsN0ahvFHX/gCAUek46MK2rFrQ/Z7+r0Vv3A == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedruddvtddgudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfhgfhffvufgjfffkgggtsehttdertddtredtnecuhfhrohhmpeghihhllhhi rghmucftrghnkhhinhcuoeifihhllhhirghmsegshigurghsvghinhdrtghomheqnecukf hppeduvddtrddvvddrjeegrdeggeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpeifihhllhhirghmsegshigurghsvghinhdrtghomh X-ME-Proxy: Original-Received: from localhost (unknown [120.22.74.44]) by mail.messagingengine.com (Postfix) with ESMTPA id 0EF983060F09; Tue, 10 Mar 2020 06:29:15 -0400 (EDT) In-reply-to: <83eeu49o48.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:177128 Archived-At: On Sun, Mar 08 2020, Eli Zaretskii wrote: > How about changing jit-lock-context-time to something like 1.5, and > checking whether this affects the frequency of the jumps in any way? Good idea. I think the difficulty with debugging this is how difficult it will be for me to solve without reliably reproducing it. > I looked at the code of the involved functions, and couldn't spot any > place where they move point without wrapping that in save-excursion. > But maybe I'm missing something -- can you see any suspects? The only thing (I'm guessing here) is that the macro with-buffer-prepared-for-jit-lock uses inhibit-point-motion-hooks which is marked obsolete since Emacs-25.1; but there's nothing in the NEWS about this. Also manually calling jit-lock-context-fontify or jit-lock-stealth-fontify doesn't move point :/ > Also, do you have any features enabled which could perform a redisplay > triggered by point movement? If you do, perhaps they cause point to > be displayed when Emacs doesn't expect that. This would only be on post-command-hook or with cursor-sensor-mode activated right? As far as I can tell I don't have any buffers with cursor-sensor-mode active, and this is the value of post-command-hook in an elisp buffer: (jit-lock--antiblink-post-command eldoc-schedule-timer t) Local in buffer binder.el; global value is (global-font-lock-mode-check-buffers global-eldoc-mode-check-buffers global-page-break-lines-mode-check-buffers) > Btw, in your original description you said when point jumps, it's > outside of the current window -- but if so, how do you see that it > jumps, when the cursor is not shown? Sorry, I was unclear. I only meant that e.g. if the window shows buffer lines 500 - 580 then point may jump to position 250, i.e. beyond the window boundaries, and the window scrolls to keep point visible. So essentially the window jumps around to follow point jumping around. > And finally, what happens if you disable the blink-cursor-mode? Done. Still a waiting game...