From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: ccsmile2008@outlook.com, npostavs@gmail.com, emacs-devel@gnu.org
Subject: Re: beginning-of-defun-comments bug [was: Re: 26.0.90: mark-defun problem in c-mode]
Date: Sat, 30 Dec 2017 14:53:27 +0200 [thread overview]
Message-ID: <83shbse5rs.fsf@gnu.org> (raw)
In-Reply-To: <20171230120136.GD10623@ACM> (message from Alan Mackenzie on Sat, 30 Dec 2017 12:01:36 +0000)
> Date: Sat, 30 Dec 2017 12:01:36 +0000
> Cc: emacs-devel@gnu.org, zhang cc <ccsmile2008@outlook.com>,
> Noam Postavsky <npostavs@gmail.com>
> From: Alan Mackenzie <acm@muc.de>
>
> > I see the error, with point anywhere in the body of the second function.
> > Critical seems to be there being no blank line between the functions.
>
> > I think there's a bug in beginning-of-defun-comments, which I'm in the
> > middle of edebugging. It moves point into the first function.
>
> beginning-of-defun-comments has a bug. On doing M-x
> beginning-of-defun-comments from the inside of a function, when there's
> no blank lines between it and the previous function, point ends up
> inside that previous function, not at the comments which may separate
> them.
>
> Perhaps this bug should be fixed before the next Emacs-26 pretest.
How old is this problem? It looks like it's new in Emacs 26? If so,
we should try fixing it on the release branch.
next prev parent reply other threads:[~2017-12-30 12:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-30 9:49 26.0.90: mark-defun problem in c-mode zhang cc
2017-12-30 10:30 ` Eli Zaretskii
2017-12-30 10:34 ` Alan Mackenzie
2017-12-30 12:01 ` beginning-of-defun-comments bug [was: Re: 26.0.90: mark-defun problem in c-mode] Alan Mackenzie
2017-12-30 12:53 ` Eli Zaretskii [this message]
2017-12-30 13:05 ` Alan Mackenzie
2018-01-03 4:51 ` Marcin Borkowski
2018-01-03 16:24 ` Alan Mackenzie
2018-01-05 14:55 ` zhang cc
2018-01-06 12:00 ` Alan Mackenzie
2018-01-06 13:54 ` zhang cc
2018-01-07 6:25 ` Marcin Borkowski
2018-03-26 6:57 ` Marcin Borkowski
2017-12-30 15:43 ` Alan Mackenzie
2017-12-30 18:43 ` Stephen Leake
2017-12-31 10:55 ` Alan Mackenzie
2017-12-31 4:26 ` Stefan Monnier
2017-12-31 10:50 ` Alan Mackenzie
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=83shbse5rs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=ccsmile2008@outlook.com \
--cc=emacs-devel@gnu.org \
--cc=npostavs@gmail.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).