all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Spencer Nelson <swnelson@uw.edu>
Cc: 49077@debbugs.gnu.org
Subject: bug#49077: 26.3; conf-mode for Java properties files uses incorrect comment syntax
Date: Sat, 16 Jul 2022 14:15:21 +0200	[thread overview]
Message-ID: <87wncdqmna.fsf@gnus.org> (raw)
In-Reply-To: <CAO-QhjWBcNXQXy6HzO8qbwSh+=mcee1TbCchD28a-V_Mp5Hhyw@mail.gmail.com> (Spencer Nelson's message of "Thu, 17 Jun 2021 10:10:19 -0700")

Spencer Nelson <swnelson@uw.edu> writes:

> The documenting comment for conf-javaprop-mode says this:
>
> "Conf Mode starter for Java properties files.
> Comments start with `#' but are also recognized with `//' or
> between `/*' and `*/'.
> For details see `conf-mode'.  Example:
>
> # Conf mode font-locks this right with \\[conf-javaprop-mode] (Java properties)
> // another kind of comment
> /* yet another */
>
> But // and /* don't start comments in Java properties files. Java
> properties files just have single-line comments starting with #.
> Somewhat obscurely, comments can also start with !.

I thought this should be easy to fix, but I'm not at all sure where the
font-locking of // and /* */ is coming from.  I feel like I've looked at
all the font-lock-* variables, but I can't find anything.

Anybody?

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





  parent reply	other threads:[~2022-07-16 12:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 17:10 bug#49077: 26.3; conf-mode for Java properties files uses incorrect comment syntax Spencer Nelson
2021-06-19 13:33 ` Lars Ingebrigtsen
2022-07-16 12:15 ` Lars Ingebrigtsen [this message]
2022-08-20  9:54   ` Lars Ingebrigtsen

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=87wncdqmna.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=49077@debbugs.gnu.org \
    --cc=swnelson@uw.edu \
    /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.