From: Stefan Kangas <stefankangas@gmail.com>
To: Theodor Thornhill <theo@thornhill.no>
Cc: acm@muc.de, 59601@debbugs.gnu.org,
"Jostein Kjønigsen" <jostein@kjonigsen.net>
Subject: bug#59601: 29.0.50; csharp-mode variables missing prefix
Date: Sun, 10 Sep 2023 12:30:06 -0700 [thread overview]
Message-ID: <CADwFkmkayt7MXDZJkoOaw5hkE9ygRdj4tDhe2g4D-PjeO8FRzQ@mail.gmail.com> (raw)
In-Reply-To: <87lenx4jbo.fsf@thornhill.no> (Theodor Thornhill's message of "Sat, 26 Nov 2022 20:16:59 +0100")
Theodor Thornhill <theo@thornhill.no> writes:
> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> Severity: wishlist
>>
>> Should these variables have the prefix `csharp-'?
>>
>> `codedoc-font-lock-doc-comments'
>> `codedoc-font-lock-keywords'
>>
>> I also see that `codedoc-font-lock-keywords' seems to be unused?
>
> I believe they need to be like this, for some CC Mode magic reason. See
> `javadoc-font-lock-keywords' and friends. I believe CC Mode picks them
> up and that they should follow that naming convention. I've CC'd Alan
> just to confirm. If you agree Alan then they could be part of
> cc-fonts.el now that csharp-mode is in core. What do you think?
Ping. Alan, do you have any comments?
next prev parent reply other threads:[~2023-09-10 19: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 [this message]
2023-09-10 20:53 ` Alan Mackenzie
2023-09-10 21:30 ` Stefan Kangas
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=CADwFkmkayt7MXDZJkoOaw5hkE9ygRdj4tDhe2g4D-PjeO8FRzQ@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=59601@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 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).