From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, 40658@debbugs.gnu.org
Subject: bug#40658: Fforward-comment: Incorrect recognition of end of comment in C++
Date: Thu, 16 Apr 2020 17:29:23 +0000 [thread overview]
Message-ID: <20200416172923.GB5235@ACM> (raw)
In-Reply-To: <83lfmveep9.fsf@gnu.org>
Hello, Eli.
On Thu, Apr 16, 2020 at 16:35:14 +0300, Eli Zaretskii wrote:
> > Date: Thu, 16 Apr 2020 12:44:26 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > Cc: Stefan Monnier <monnier@iro.umontreal.ca>
> > This should clearly go into the master branch. I think it should also go
> > into the emacs-27 release branch, since it is relevant for a nasty bug,
> > bug #40052.
> Sorry, too late for that now. This code is there for the last 20+
> years, we can endure that a bit more, I think.
OK, I've committed the patch to master. The code, in effect, just dates
from 2015, when I added support for escaped EOLs in comments.
I will put some workaround into CC Mode (which I would have to have done
anyway).
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2020-04-16 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 12:44 bug#40658: Fforward-comment: Incorrect recognition of end of comment in C++ Alan Mackenzie
2020-04-16 13:35 ` Eli Zaretskii
2020-04-16 17:29 ` Alan Mackenzie [this message]
2020-04-16 18:01 ` Stefan Monnier
[not found] ` <handler.40658.B.158704107627532.ack@debbugs.gnu.org>
2020-04-16 17:31 ` bug#40658: (Fforward-comment: Incorrect recognition of end of comment in C++) 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=20200416172923.GB5235@ACM \
--to=acm@muc.de \
--cc=40658@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).