From: Eli Zaretskii <eliz@gnu.org>
To: Eshel Yaron <me@eshelyaron.com>
Cc: 72759@debbugs.gnu.org
Subject: bug#72759: 31.0.50; Emacs hangs with open-paren-in-column-0-is-defun-start set to nil
Date: Thu, 22 Aug 2024 16:54:24 +0300 [thread overview]
Message-ID: <86msl4slwv.fsf@gnu.org> (raw)
In-Reply-To: <m1msl4ente.fsf@dazzs-mbp.home> (message from Eshel Yaron on Thu, 22 Aug 2024 14:37:01 +0200)
> From: Eshel Yaron <me@eshelyaron.com>
> Cc: 72759@debbugs.gnu.org
> Date: Thu, 22 Aug 2024 14:37:01 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Would it make sense to have checkdoc-next-docstring bind
> > open-paren-in-column-0-is-defun-start to a non-nil value?
>
> Not entirely: the difference in behavior of beginning-of-defun is
> unexpected, and may prove problematic in other cases as well, so it
> would be best to fix the root cause IMO. Namely, in
> beginning-of-defun-raw, the fallback cond clause fails to move forward
> over an sexp that does starts after the beginning of the line.
How do you propose to fix the root cause, when Emacs fails to
correctly identify the beginning of a defun? Suppose we'd want to fix
the condition of this loop:
>> (while (and (not (setq found (checkdoc--next-docstring)))
>> (beginning-of-defun -1)))
so it doesn't infloop -- how would you go about that, when
beginning-of-defun doesn't move and you are not at BOB?
> You should also be able to see this in effect with C-- C-M-a at the
> beginning of a line whose contents is " (foo)". The results vary
> depending on the value of open-paren-in-column-0-is-defun-start.
Exactly! When beginning-of-defun is confused, what are its callers
supposed to do? They don't know better where the beginning of the
previous defun is.
Or what am I missing?
next prev parent reply other threads:[~2024-08-22 13:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 10:07 bug#72759: 31.0.50; Emacs hangs with open-paren-in-column-0-is-defun-start set to nil Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-22 10:56 ` Eli Zaretskii
2024-08-22 11:31 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-22 12:12 ` Eli Zaretskii
2024-08-22 12:37 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-22 13:54 ` Eli Zaretskii [this message]
2024-08-22 15:49 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-22 16:10 ` Eli Zaretskii
2024-08-22 17:08 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-22 17:54 ` Eli Zaretskii
2024-08-23 5:54 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-23 6:56 ` Eli Zaretskii
2024-08-23 8:33 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-23 13:14 ` Eli Zaretskii
2024-08-23 15:22 ` Eshel Yaron 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=86msl4slwv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72759@debbugs.gnu.org \
--cc=me@eshelyaron.com \
/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).