all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Toon Claes <toon@iotcl.com>
Cc: Toon Claes <toon@tonotdo.com>, 11865@debbugs.gnu.org
Subject: bug#11865: Fwd: Re: 24.1.50; doxygen comments not highlighted in c++-mode
Date: Sat, 27 Feb 2016 14:34:29 +1030	[thread overview]
Message-ID: <87d1rilrxu.fsf@gnus.org> (raw)
In-Reply-To: <0C474D0B-86AF-4030-B4B4-87E8CBEC4A67@iotcl.com> (Toon Claes's message of "Fri, 26 Feb 2016 09:03:27 +0100")

Toon Claes <toon@iotcl.com> writes:

> I do not really agree.
>
> Let me explain in detail.
> Only comment blocks like the following were recognized as gtkdoc:
> /**
>  * This is the gtkdoc comment
>  */
>
> I wanted also gtkdoc styling to be applied to:
> /** This should be gtkdoc comment too */
>
> I admit, the regexp I wrote back in the day was not correctly escaped.
> But I was trying to achieve comments with 3 or more asterisks would
> not get styled like gtkdoc comments.

Can you supply a patch that will give the correct styling?

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





  reply	other threads:[~2016-02-27  4:04 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
2016-02-26  8:03     ` Toon Claes
2016-02-27  4:04       ` Lars Ingebrigtsen [this message]
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=87d1rilrxu.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=11865@debbugs.gnu.org \
    --cc=toon@iotcl.com \
    --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.