From: Eli Zaretskii <eliz@gnu.org>
To: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
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:03:10 +0300 [thread overview]
Message-ID: <83mswuzagx.fsf@gnu.org> (raw)
In-Reply-To: <87leceo2ns.fsf@sappc2.fritz.box> (message from Jens Schmidt on Sat, 07 Oct 2023 17:47:19 +0200)
> From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
> Cc: 66218@debbugs.gnu.org
> Date: Sat, 07 Oct 2023 17:47:19 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
> >> Cc: Eli Zaretskii <eliz@gnu.org>
> >> Date: Fri, 06 Oct 2023 21:26:24 +0200
> >
> > I'm afraid I cannot reproduce the original problem using the current
> > emacs-29 branch. Typing C-M-a from buffer position 70719 in shr.el
> > from emacs-29 lands me at the beginning of shr-table-body, as
> > expected.
>
> Thanks for looking into this, but it still reproduces for me.
>
> It is important to execute the reproducer *without* actually getting the
> file to the glass, so hitting C-M-a in the file itself would not show
> the issue.
Why not? If the problem is where you identify it, it should not
matter how beginning-of-defun is invoked.
I'm not being stubborn, mind you, I think it's important that we
understand the issue completely to reason about the solutions. And I
think we don't yet have a sufficient understanding of the problem, or
at least I don't.
> Please try exactly like described below, starting off the
> root of the development directory:
>
> ------------------------- snip -------------------------
> [emacs-29]$ pwd
> /home/jschmidt/work/emacs-29
> [emacs-29]$ ls -al README
> -rw-r--r-- 1 jschmidt jschmidt 6125 Aug 1 00:06 README
> [emacs-29]$ git rev-parse HEAD
> 8f23a02a9ea1fbc4213cae5664dcb9bf6b5205f6
> [emacs-29]$ make -j8
> make actual-all || make advice-on-failure make-target=all exit-status=$?
> make[1]: Entering directory '/home/jschmidt/work/emacs-29'
> [...]
> make[1]: Leaving directory '/home/jschmidt/work/emacs-29'
> [emacs-29]$ ./src/emacs -Q
> ------------------------- snip -------------------------
>
> Paste the following form into the scratch buffer with C-y:
>
> ------------------------- snip -------------------------
> (progn
> (with-current-buffer
> (find-file-noselect "lisp/net/shr.el")
> (goto-char 70719)
> (beginning-of-defun)
> ;; point should be at BOF of `shr-table-body', but is in fact
> ;; somewhere near a Unicode character name
> (pop-to-buffer (current-buffer))))
> ------------------------- snip -------------------------
>
> And immediately after that hit C-x C-e. It lands me to the position
> denoted by "^" (point=68645 of 91908):
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. And if it turns out that the problem is
so hard to reproduce, maybe we don't have to fix it on emacs-29.
next prev parent reply other threads:[~2023-10-07 16:03 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 [this message]
2023-10-07 17:39 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83mswuzagx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66218@debbugs.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.