unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Bastian Beischer <bastian.beischer@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 28939@debbugs.gnu.org
Subject: bug#28939: 27.0.50; CC-Mode: (C++) Comment directly after quote breaks following lines
Date: Mon, 30 Nov 2020 13:55:21 +0100	[thread overview]
Message-ID: <CAK9AuB-v26YXx9F+jTVaN7wKZPk0_fWZjec0-OQvkM+Q4ANPKQ@mail.gmail.com> (raw)
In-Reply-To: <87sg8rcehf.fsf@gnus.org>

Hello Lars,

On Mon, Nov 30, 2020 at 11:43 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> Bastian Beischer <bastian.beischer@gmail.com> writes:
>
> > The following file is incorrectly parsed by CC-Mode (font-lock
> > considers everything after //bar to be a comment, for example):
> >
> > #include "foo.h"//bar
> > int main(int argc, char** argv) {
> >   return 0;
> > }
> >
> > This problem is reproduceable from emacs -Q when inserting the above
> > into a c++-mode buffer.
> >
> > This is with emacs built from 94281c9a1cc0f756841fdc9b266657853df94a29
> > on master, but I guess this is relevant for emacs-26 as well.
>
> (This bug report unfortunately got no response at the time.)
>
> I'm unable to reproduce this in Emacs 26.1, 27.1 or the current trunk.
> For instance, in Emacs 26.1, it displays as:
>
>
> which looks correct to me.
>
> Are you still seeing this problem, or has it been fixed in the meantime?

Yes, it seems it's fixed. Thanks for following up!

Cheers
Bastian

>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-11-30 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-22  8:12 bug#28939: 27.0.50; CC-Mode: (C++) Comment directly after quote breaks following lines Bastian Beischer
2020-11-30 10:42 ` Lars Ingebrigtsen
2020-11-30 12:55   ` Bastian Beischer [this message]
2020-11-30 13:00     ` Lars Ingebrigtsen

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=CAK9AuB-v26YXx9F+jTVaN7wKZPk0_fWZjec0-OQvkM+Q4ANPKQ@mail.gmail.com \
    --to=bastian.beischer@gmail.com \
    --cc=28939@debbugs.gnu.org \
    --cc=larsi@gnus.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 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).