From: Jonathon McKitrick <jcm@SDF.ORG>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 62216@debbugs.gnu.org
Subject: bug#62216: Odd file corruption in clojure mode and emacs 30 HEAD
Date: Tue, 16 May 2023 20:22:24 +0000 [thread overview]
Message-ID: <ZGPmADIKCSwwgz1b@SDF.ORG> (raw)
In-Reply-To: <83edppqjfl.fsf@gnu.org>
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 <jcm@SDF.ORG>
: >
: > 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 <something> to trigger the corrption
: . observe the changes in the file's contents:
: - <description of the corruptions>
:
: 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.'
next prev parent reply other threads:[~2023-05-16 20:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 0:01 bug#62216: Odd file corruption in clojure mode and emacs 30 HEAD Jonathon McKitrick
2023-03-16 6:50 ` Eli Zaretskii
2023-05-16 20:22 ` Jonathon McKitrick [this message]
2023-05-17 11:35 ` Eli Zaretskii
2023-07-27 1:42 ` Dmitry Gutov
2023-08-30 7:50 ` Gerd Möllmann
2023-08-30 11:20 ` Dmitry Gutov
2023-07-23 13:58 ` bug#62216: Narrowing down the issue Jonathon McKitrick via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-23 14:35 ` bug#62216: Odd file corruption in clojure mode and emacs 30 HEAD Eli Zaretskii
2023-07-25 10:09 ` Jonathon McKitrick via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-25 10:34 ` Jonathon McKitrick via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 13:38 ` bug#62216: Narrowed the issue to one line Jonathon McKitrick via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 15:26 ` Eli Zaretskii
2023-08-20 19:13 ` Paul Eggert
2023-08-20 19:19 ` Eli Zaretskii
2023-08-20 20:11 ` Paul Eggert
2023-08-20 22:21 ` Jonathon McKitrick via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-22 13:08 ` Jonathon McKitrick via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-22 14:10 ` Paul Eggert
2023-08-22 15:41 ` Eli Zaretskii
2023-08-22 23:29 ` Paul Eggert
2023-08-21 8:43 ` Jonathon McKitrick via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-21 9:17 ` Jonathon McKitrick via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-21 9:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-30 8:59 ` bug#62216: Odd file corruption in clojure mode and emacs 30 HEAD Gerd Möllmann
2023-08-30 12:00 ` Eli Zaretskii
2023-08-30 12:07 ` Gerd Möllmann
2023-08-31 14:46 ` Jonathon McKitrick via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-31 15:54 ` Eli Zaretskii
2023-09-01 1:17 ` Jonathon McKitrick via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZGPmADIKCSwwgz1b@SDF.ORG \
--to=jcm@sdf.org \
--cc=62216@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).