From: Stefan Kangas <stefankangas@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: "Jostein Kjønigsen" <jostein@kjonigsen.net>,
59601-done@debbugs.gnu.org,
"Theodor Thornhill" <theo@thornhill.no>
Subject: bug#59601: 29.0.50; csharp-mode variables missing prefix
Date: Sun, 10 Sep 2023 14:30:26 -0700 [thread overview]
Message-ID: <CADwFkmmWowRXAMk9NFQELoKVQEMUiYFpmDJ9=RGM5y=39x21Zw@mail.gmail.com> (raw)
In-Reply-To: <ZP4szViIuntf42zE@ACM>
Alan Mackenzie <acm@muc.de> writes:
> The codedoc variables should _not_ have a csharp- prefix. Conceptually,
> codedoc is not part of csharp-mode, and could start being used by any CC
> Mode mode, just as gtkdoc is used by both C and C++ modes.
>
> Also, "codedoc" (like "gtkdoc", etc.) is prefixed to
> "-font-lock-doc-comments" and the result interned to get the function to
> fontify the doc comments. Thus codedoc-font-lock-doc-comments _will_ be
> getting used.
>
> So, yes, the naming convention is essential to the working of CC Mode's
> doc comments.
>
> Whether it would be the Right Thing to add codedoc to CC Mode itself,
> I'm not sure. doxygen was added quite recently, but that is genuinely a
> language independent format. I'm a little worried about getting some
> coupling between, say, csharp-mode and CC Mode where there wasn't any
> before.
Thank you, that clears things up. I agree that we should not do any
changes here, and we certainly want to avoid any coupling if we don't
need it. Thank you for taking the time to explain.
I opened this bug, so I hope that it will be fine if I close it.
I'm therefore doing that with this email.
prev parent reply other threads:[~2023-09-10 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 8:03 bug#59601: 29.0.50; csharp-mode variables missing prefix Stefan Kangas
2022-11-26 19:16 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 19:30 ` Stefan Kangas
2023-09-10 20:53 ` Alan Mackenzie
2023-09-10 21:30 ` Stefan Kangas [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='CADwFkmmWowRXAMk9NFQELoKVQEMUiYFpmDJ9=RGM5y=39x21Zw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=59601-done@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=jostein@kjonigsen.net \
--cc=theo@thornhill.no \
/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.