From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jonathon McKitrick Newsgroups: gmane.emacs.bugs Subject: bug#62216: Odd file corruption in clojure mode and emacs 30 HEAD Date: Tue, 16 May 2023 20:22:24 +0000 Message-ID: References: <83edppqjfl.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20865"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 62216@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue May 16 22:23:21 2023 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 1pz1Cb-0005CK-1m for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 16 May 2023 22:23:21 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pz1CK-0004pO-MQ; Tue, 16 May 2023 16:23:04 -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 1pz1CI-0004ok-7s for bug-gnu-emacs@gnu.org; Tue, 16 May 2023 16:23:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pz1CI-00039k-07 for bug-gnu-emacs@gnu.org; Tue, 16 May 2023 16:23:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pz1CH-0007PR-SA for bug-gnu-emacs@gnu.org; Tue, 16 May 2023 16:23:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Jonathon McKitrick Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 16 May 2023 20:23:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 62216 X-GNU-PR-Package: emacs Original-Received: via spool by 62216-submit@debbugs.gnu.org id=B62216.168426855328414 (code B ref 62216); Tue, 16 May 2023 20:23:01 +0000 Original-Received: (at 62216) by debbugs.gnu.org; 16 May 2023 20:22:33 +0000 Original-Received: from localhost ([127.0.0.1]:48155 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pz1Bp-0007OE-IO for submit@debbugs.gnu.org; Tue, 16 May 2023 16:22:33 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:55949) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pz1Bk-0007O2-Hd for 62216@debbugs.gnu.org; Tue, 16 May 2023 16:22:32 -0400 Original-Received: from sdf.org (IDENT:jcm@sdf.org [205.166.94.16]) by mx.sdf.org (8.16.1/8.14.5) with ESMTPS id 34GKMPQ3027917 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Tue, 16 May 2023 20:22:26 GMT DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sdf.org; s=my-selector-name; t=1684268546; bh=JIMhEAZ1suHuP+7Z0BMpfHYeno+sPEvUemvzk6N71XU=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=T8i0UlPPXL/piUUtFcFQjAnyWk2SF3DpdUaktTe2xz6clgi4lvjRy+7LIaGnF9Alm muZCX5X5xe8X3+Lph6zmLFgm1/JJHDrmKqoBRaVF//4jQyBvQvUcQ3CN9lb1kV5/qG qWRENdnSrTI/zYkjC1JLhTLcUW5af5JfdLGijmD8= Original-Received: (from jcm@localhost) by sdf.org (8.16.1/8.12.8/Submit) id 34GKMO8m010841; Tue, 16 May 2023 20:22:24 GMT Content-Disposition: inline In-Reply-To: <83edppqjfl.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:261814 Archived-At: On Thu, Mar 16, 2023 at 08:50:06AM +0200, Eli Zaretskii wrote: : > Date: Thu, 16 Mar 2023 00:01:12 +0000 : > From: Jonathon McKitrick : > : > I realize this is vague, but I'm seeing it consistently: : > : > I build emacs 30 with native compilation on my M1, and I open my work clojure project, and I see rainbow parens marking a bunch of unmatched parens. : > The file will not compile, and the corruption happens simply when I open the file. : > : > I do the exact same thing with emacs 29 built the same way, and I have no issues. : > : > How can I narrow this down to a useful bug report? : : Thanks for asking, and for the bug report in the first place. : : The way to narrow this down is start with "emacs -Q", add only those : of your customizations necessary for reproducing the problem, then : post the results in the form of step by step description of the : reproduction recipe. It will help a lot if you also post the file : which gets corrupted, both before and after the corruption. If that : file can be small, that's preferable. : : I'm guessing that you use some third-party packages, at least for : editing clojure sources. In that case, include in your description : the packages one should download to reproduce the issue. : : A description of the recipe should, therefore, look something like the : following: : : . download and install the following packages: : - foo : - bar : - ... : . start "emacs -Q" : . type the following commands: : - M-x load-library RET foo RET : - M-x load-library RET bar RET : - M-x set-variable RET foo-some-var RET t RET : -... : . visit the attached file foobar.clj : . do to trigger the corrption : . observe the changes in the file's contents: : - : : TIA I'm frustrated that I cannot reproduce the bug reliably, but it does happen constantly under emacs 30. What I have narrowed it down to is what seems to be a random injection of code from the same file or the kill ring. That of course trips up paredit and any compilation. I check the messages, and cannot tell if there's a random command or key binding that triggers a random command responsible for the issue. I happens with and without native compilation. Since I cannot predict *when* it's going to happen, it's difficult to get work done with packages disabled, not knowing when I'll see the bug. Has anything like this been reported anywhere else? Jonathon McKitrick -- 'My other computer is your Linux box.'