From: Lars Ingebrigtsen <larsi@gnus.org>
To: Toon Claes <toon@tonotdo.com>
Cc: 11865@debbugs.gnu.org
Subject: bug#11865: Fwd: Re: 24.1.50; doxygen comments not highlighted in c++-mode
Date: Fri, 26 Feb 2016 14:07:05 +1030 [thread overview]
Message-ID: <87y4a8m9b2.fsf@gnus.org> (raw)
In-Reply-To: <16d1f96d86592f9e5511b61a678e2f81@tonotdo.com> (Toon Claes's message of "Wed, 05 Jun 2013 10:24:56 +0200")
Toon Claes <toon@tonotdo.com> writes:
> (defconst gtkdoc-font-lock-keywords
> `((,(lambda (limit)
> - (c-font-lock-doc-comments "/**$" limit
> + (c-font-lock-doc-comments "/**([^*/].*)?$" limit
Can this be correct, though? It would mean that /** foo / **/ wouldn't
be a comment... and anyway, the /** is invalid as a regexp, anyway.
The current code looks like
(defconst gtkdoc-font-lock-keywords
`((,(lambda (limit)
(c-font-lock-doc-comments "/\\*\\*$" limit
gtkdoc-font-lock-doc-comments)
(c-font-lock-doc-comments "/\\*< " limit
gtkdoc-font-lock-doc-protection)
))))
Which looks more correct anyway. So I think this has already been fixed
in a different manner, and I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-02-26 3:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 11:46 bug#11865: 24.1.50; doxygen comments not highlighted in c++-mode Toon Claes
2012-07-06 14:00 ` Toon Claes
2012-07-10 6:59 ` Toon Claes
2016-02-24 6:29 ` Lars Ingebrigtsen
2013-06-05 8:24 ` bug#11865: Fwd: " Toon Claes
2016-02-26 3:37 ` Lars Ingebrigtsen [this message]
2016-02-26 8:03 ` Toon Claes
2016-02-27 4:04 ` Lars Ingebrigtsen
2016-03-10 8:58 ` Toon Claes
2019-06-27 15:10 ` Lars Ingebrigtsen
2019-06-28 9:19 ` Alan Mackenzie
2019-06-30 15:13 ` Alan Mackenzie
2019-07-01 7:49 ` Toon Claes
2019-07-03 2:36 ` Basil L. Contovounesios
2016-02-25 6:01 ` bug#11865: " Anders Lindgren
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=87y4a8m9b2.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=11865@debbugs.gnu.org \
--cc=toon@tonotdo.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.