From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "N. Raghavendra" <raghu@hri.res.in>
Cc: 28428@debbugs.gnu.org
Subject: bug#28428: comment-search-backward with no comments
Date: Fri, 22 Sep 2017 12:40:58 -0400 [thread overview]
Message-ID: <jwv1smywv0z.fsf-monnier+bug#28428@gnu.org> (raw)
In-Reply-To: <87377seua8.fsf@ailuros> (N. Raghavendra's message of "Tue, 12 Sep 2017 04:07:35 +0530")
> (if (not (re-search-backward comment-start-skip limit t))
> - (unless noerror (error "No comment"))
> + (progn
> + (goto-char limit)
> + (unless noerror (error "No comment")))
That looks fine, thank you. But I think the simpler patch below works
as well:
diff --git a/lisp/newcomment.el b/lisp/newcomment.el
index be6dbe3a4c..e32966e596 100644
--- a/lisp/newcomment.el
+++ b/lisp/newcomment.el
@@ -524,7 +524,7 @@ comment-search-backward
;; comment-search-backward is only used to find the comment-column (in
;; comment-set-column) and to find the comment-start string (via
;; comment-beginning) in indent-new-comment-line, it should be harmless.
- (if (not (re-search-backward comment-start-skip limit t))
+ (if (not (re-search-backward comment-start-skip limit 'move))
(unless noerror (error "No comment"))
(beginning-of-line)
(let* ((end (match-end 0))
I wonder if there's code out there that depends on this behavior, tho,
since AFAIK it's been behaving this way "forever".
Stefan
next prev parent reply other threads:[~2017-09-22 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 22:37 bug#28428: comment-search-backward with no comments N. Raghavendra
2017-09-22 16:40 ` Stefan Monnier [this message]
2017-09-22 17:48 ` N. Raghavendra
2017-09-22 19:26 ` Stefan Monnier
2017-09-22 20:31 ` N. Raghavendra
2017-09-23 21:07 ` Stefan Monnier
2017-09-24 0:26 ` N. Raghavendra
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='jwv1smywv0z.fsf-monnier+bug#28428@gnu.org' \
--to=monnier@iro.umontreal.ca \
--cc=28428@debbugs.gnu.org \
--cc=raghu@hri.res.in \
/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).