From: Jens Schmidt via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 66218@debbugs.gnu.org
Subject: bug#66218: 29.1.50; `beginning-of-defun' jumps to wrong position in `emacs-lisp-mode'
Date: Sat, 07 Oct 2023 19:39:52 +0200 [thread overview]
Message-ID: <87h6n2nxg7.fsf@sappc2.fritz.box> (raw)
In-Reply-To: <83mswuzagx.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 07 Oct 2023 19:03:10 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
>> Cc: 66218@debbugs.gnu.org
>> Date: Sat, 07 Oct 2023 17:47:19 +0200
> I'm surprised, to say the least, that such a simple bug needs such a
> complex reproducer, and any deviation from it fails the recipe. I
> think we must understand why.
As soon as you find the file and it's displayed in a window, a lot of
things happen even in an "emacs -Q" that set syntax properties in the
buffer. With these syntax properties already being set, the bug won't
reproduce.
But here is an interactive-only reproducer (which comes close to my
truth, btw, I don't use eldoc-mode or show-paren-mode):
emacs -Q
C-- M-x global-font-lock-mode RET
C-- M-x global-eldoc-mode RET
C-- M-x show-paren-mode RET
C-x C-f lisp/net/shr.el RET
M-x goto-char RET 70719 RET
C-M-a
Ends up on point=68645 of 91908 for me.
> And if it turns out that the problem is so hard to reproduce, maybe we
> don't have to fix it on emacs-29.
Even if the patch is so innocent as adding a `save-match-data' in the
right place?
next prev parent reply other threads:[~2023-10-07 17:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 19:40 bug#66218: 29.1.50; `beginning-of-defun' jumps to wrong position in `emacs-lisp-mode' Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-28 0:59 ` No Wayman
2023-09-28 19:43 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-30 23:48 ` Stefan Kangas
2023-10-06 19:26 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-07 6:08 ` Eli Zaretskii
2023-10-07 15:47 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-07 16:03 ` Eli Zaretskii
2023-10-07 17:39 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-10-07 18:22 ` Eli Zaretskii
2023-10-07 20:31 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 8:03 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6n2nxg7.fsf@sappc2.fritz.box \
--to=bug-gnu-emacs@gnu.org \
--cc=66218@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jschmidt4gnu@vodafonemail.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.