all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alan Mackenzie <acm@muc.de>
Cc: Li Feng <li.feng@snap.com>, 33973@debbugs.gnu.org
Subject: bug#33973: Multi-line C++ raw string literal font lock is broken
Date: Wed, 01 Sep 2021 11:15:01 +0200	[thread overview]
Message-ID: <87fsuofyi2.fsf@gnus.org> (raw)
In-Reply-To: <20190107152549.49324.qmail@mail.muc.de> (Alan Mackenzie's message of "7 Jan 2019 15:25:49 -0000")

[-- Attachment #1: Type: text/plain, Size: 537 bytes --]

Alan Mackenzie <acm@muc.de> writes:

>> Write a multi-line raw string literal in c++-mode, and font
>> lock doesn't show the correct syntax highlighting. Sample code:
>
>> const char* s1 = R"foo(
>> Hello
>> World
>> )foo";
>
>> const char* s2 = R"(
>> Hello
>> World
>> )";
>
> Yes.  Thank you for reporting this bug.  I'm working on fixing it, and
> hope to commit a patch to master sometime in the next few days.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

Testing this in Emacs 28, I get:


[-- Attachment #2: Type: image/png, Size: 11467 bytes --]

[-- Attachment #3: Type: text/plain, Size: 333 bytes --]


Which...  I think is correct?  So I guess this has been fixed in the
years since this was reported, and I'm closing this bug report.  (If
there's still bugs in this area, please respond to the debbugs address
and we'll reopen.)

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

      reply	other threads:[~2021-09-01  9:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04  5:21 bug#33973: Multi-line C++ raw string literal font lock is broken Li Feng
     [not found] ` <mailman.6748.1546581187.1284.bug-gnu-emacs@gnu.org>
2019-01-07 15:25   ` Alan Mackenzie
2021-09-01  9:15     ` Lars Ingebrigtsen [this message]

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=87fsuofyi2.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=33973@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=li.feng@snap.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 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.