From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, zhang cc <ccsmile2008@outlook.com>
Subject: Re: 26.0.90: mark-defun problem in c-mode
Date: Sat, 30 Dec 2017 10:34:32 +0000 [thread overview]
Message-ID: <20171230103432.GB10623@ACM> (raw)
In-Reply-To: <834lo8fqyi.fsf@gnu.org>
Hello, Eli and Zhang.
On Sat, Dec 30, 2017 at 12:30:29 +0200, Eli Zaretskii wrote:
> > From: zhang cc <ccsmile2008@outlook.com>
> > Date: Sat, 30 Dec 2017 09:49:17 +0000
> >
> > When cursor is in the second function body, mark-defun can’t mark
> > the second function.
> "M-x mark-defun" works fine here with your example. Where exactly
> should cursor be in the second function body to reproduce the problem?
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.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-12-30 10:34 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171230103432.GB10623@ACM \
--to=acm@muc.de \
--cc=ccsmile2008@outlook.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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.